From: Bo YU <tsu.yubo@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] include/linux: delete duplicated kernel.h in nodemask.h
Date: Mon, 27 Apr 2020 08:32:41 +0800 [thread overview]
Message-ID: <20200427003239.kafheof34qn2bg76@host> (raw)
In-Reply-To: <20200426170942.GB2139089@kroah.com>
On Sun, Apr 26, 2020 at 07:09:42PM +0200, Greg KH wrote:
>On Sun, Apr 26, 2020 at 11:42:35PM +0800, Bo YU wrote:
>> In nodemask.h, it includes bitmap.h which has included kernel.h,
>> so delete kernel.h from nodemask file.
>>
>> Signed-off-by: Bo YU <tsu.yubo@gmail.com>
>> ---
>> BTW, I do not get maintainer of the get_maintainer file, so i do
>> not know who can accept the patch if it is right.
>> ---
>> include/linux/nodemask.h | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/include/linux/nodemask.h b/include/linux/nodemask.h
>> index 27e7fa36f707..980b48e05d05 100644
>> --- a/include/linux/nodemask.h
>> +++ b/include/linux/nodemask.h
>> @@ -46,7 +46,7 @@
>> * int next_node(node, mask) Next node past 'node', or MAX_NUMNODES
>> * int next_node_in(node, mask) Next node past 'node', or wrap to first,
>> * or MAX_NUMNODES
>> - * int first_unset_node(mask) First node not set in mask, or
>> + * int first_unset_node(mask) First node not set in mask, or
>> * MAX_NUMNODES
>> *
>> * nodemask_t nodemask_of_node(node) Return nodemask with bit 'node' set
>
>That change is not described above :(
I promise i just delete kernel.h in the nodemask file. I am wonder why
change the comment also :)
>
prev parent reply other threads:[~2020-04-27 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 15:42 [PATCH -next] include/linux: delete duplicated kernel.h in nodemask.h Bo YU
2020-04-26 17:09 ` Greg KH
2020-04-27 0:32 ` Bo YU [this message]
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=20200427003239.kafheof34qn2bg76@host \
--to=tsu.yubo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).