From: Wei Yang <richard.weiyang@gmail.com>
To: NeilBrown <neilb@suse.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
shli@fb.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bitops.h: use BITS_PER_LONG to simplify BITS_TO_LONGS
Date: Wed, 3 May 2017 09:06:00 +0800 [thread overview]
Message-ID: <20170503010600.GA12359@WeideMacBook-Pro.local> (raw)
In-Reply-To: <878tmfq6fr.fsf@notabene.neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
On Wed, May 03, 2017 at 07:45:12AM +1000, NeilBrown wrote:
>On Tue, May 02 2017, Wei Yang wrote:
>
>> Hi, masters
>>
>> Not sure this one is acceptable?
>
>You'd have better luck getting a response if you post things like this
>to akpm - he tends to collect miscellaneous bits and pieces.
>I don't think the patch makes more that a tiny improvement and I
>wouldn't bother with it, but maybe Andrew will.
>
>NeilBrown
>
Yep, thanks for your comment :-)
--
Wei Yang
Help you, Help me
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-05-03 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 0:37 [PATCH] bitops.h: use BITS_PER_LONG to simplify BITS_TO_LONGS Wei Yang
2017-05-02 13:28 ` Wei Yang
2017-05-02 21:45 ` NeilBrown
2017-05-03 1:06 ` Wei Yang [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=20170503010600.GA12359@WeideMacBook-Pro.local \
--to=richard.weiyang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=shli@fb.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