From: Alex Shi <alex.shi@intel.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
paul.gortmaker@windriver.com, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpumask: add a few comments of cpumask functions
Date: Mon, 16 Jul 2012 16:01:51 +0800 [thread overview]
Message-ID: <5003CA6F.3050806@intel.com> (raw)
In-Reply-To: <87hat8xin5.fsf@rustcorp.com.au>
On 07/16/2012 03:35 PM, Rusty Russell wrote:
> On Mon, 16 Jul 2012 10:34:46 +0800, Alex Shi <alex.shi@intel.com> wrote:
>>>
>>
>>> And the same applies to the other comments. So can you please grab the
>>> latest linux-next, prepare a fixup patch and also check that the patch
>>> is complete - not all of your changes have been applied.
>>>
>>
>>
>>
>> Thanks for reminder! I just know this rule now. :)
>
> Thanks, folded.
>
> As long as it's readable, I don't care.
>
> If it's not all there, did I miss an update?
No. all contents in my original patch were checked in.
>
> Cheers,
> Rusty.
next prev parent reply other threads:[~2012-07-16 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 9:02 [PATCH] cpumask: add a few comments of cpumask functions Alex Shi
2012-05-28 12:47 ` Srivatsa S. Bhat
2012-05-28 13:49 ` Alex Shi
2012-05-28 14:23 ` Alex Shi
2012-07-13 22:37 ` Andrew Morton
2012-07-16 2:34 ` Alex Shi
2012-07-16 7:35 ` Rusty Russell
2012-07-16 8:01 ` Alex Shi [this message]
2012-05-28 15:25 ` Srivatsa S. Bhat
2012-05-29 1:16 ` Alex Shi
2012-05-30 10:40 ` Alex Shi
2012-05-30 10:49 ` KOSAKI Motohiro
2012-05-31 8:15 ` Alex Shi
2012-06-04 1:37 ` Rusty Russell
2012-06-04 1:36 ` Rusty Russell
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=5003CA6F.3050806@intel.com \
--to=alex.shi@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rusty@rustcorp.com.au \
--cc=srivatsa.bhat@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.