linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: John Hubbard <jhubbard@nvidia.com>,
	peng8420.li@gmail.com, linux-mm@kvack.org,
	akpm@linux-foundation.org
Cc: osalvador@suse.de, jgg@ziepe.ca, peterx@redhat.com,
	linux-kernel@vger.kernel.org, dan.j.williams@intel.com
Subject: Re: [PATCH v2 2/2] Fix the source file annotation information for the "FOLL_WRITE" macro copied.
Date: Fri, 14 Nov 2025 22:41:15 +0100	[thread overview]
Message-ID: <8fd2def3-addd-4abb-976a-857611871d1d@kernel.org> (raw)
In-Reply-To: <70d7ef58-8556-4aa4-86c8-b7ed79505471@nvidia.com>

On 14.11.25 21:26, John Hubbard wrote:
> On 11/14/25 8:11 AM, peng8420.li@gmail.com wrote:
>> From: "peng8420.li" <peng8420.li@gmail.com>
> 
> Please see my reply to patch 1/1, about the real name, and the
> From: item too.
> 
>>
>> The 'FOLL_RITE' of the copied source is located in mm_types. h of mm, not mm. h, so fix it.
> 
> "FOLL_WRITE"
> 
> Also, please wrap to 72 columns.
> 
>>
>> Suggested-by: "David Hildenbrand (Red Hat)" <david@kernel.org>
>> Signed-off-by: peng8420.li <peng8420.li@gmail.com>
>> ---
>>   tools/testing/selftests/mm/gup_test.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/testing/selftests/mm/gup_test.c b/tools/testing/selftests/mm/gup_test.c
>> index 75f7134d529d..40c1538a17b4 100644
>> --- a/tools/testing/selftests/mm/gup_test.c
>> +++ b/tools/testing/selftests/mm/gup_test.c
>> @@ -17,7 +17,7 @@
>>   
>>   #define MB (1UL << 20)
>>   
>> -/* Just the flags we need, copied from mm.h: */
>> +/* Just the flags we need, copied from the kernel internals. */
>>   #define FOLL_WRITE	0x01	/* check pte is writable */
>>   
>>   #define GUP_TEST_FILE "/sys/kernel/debug/gup_test"
> 
> With the commit log fixed up, please feel free to add:
> 
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>

And here the subject should likely be:

"selftests/mm: gup_test: fix comment regarding origin of FOLL_WRITE"

It's usually a good idea to take a look at "git log -s $FILE" to see
how previous commits came up with a subject.


-- 
Cheers

David


  reply	other threads:[~2025-11-14 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 16:11 [PATCH v2 1/2] Remove the "FOLL_TOUCH" test code from gup_test.c peng8420.li
2025-11-14 16:11 ` [PATCH v2 2/2] Fix the source file annotation information for the "FOLL_WRITE" macro copied peng8420.li
2025-11-14 20:26   ` John Hubbard
2025-11-14 21:41     ` David Hildenbrand (Red Hat) [this message]
2025-11-14 20:24 ` [PATCH v2 1/2] Remove the "FOLL_TOUCH" test code from gup_test.c John Hubbard
2025-11-14 21:37   ` David Hildenbrand (Red Hat)
2025-11-14 21:39   ` David Hildenbrand (Red Hat)
2025-11-17  7:09     ` peng li
2025-11-17  7:05   ` peng li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8fd2def3-addd-4abb-976a-857611871d1d@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=osalvador@suse.de \
    --cc=peng8420.li@gmail.com \
    --cc=peterx@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox