From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org,
Venkatesh Pallipadi <venki@google.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH 12/12] cpumask: remove old cpu_*_map.
Date: Wed, 15 Feb 2012 15:06:00 +0530 [thread overview]
Message-ID: <4F3B7C80.2080802@linux.vnet.ibm.com> (raw)
In-Reply-To: <1329281884.18410.rusty@rustcorp.com.au>
On 02/15/2012 10:28 AM, Rusty Russell wrote:
> From: Rusty Russell <rusty@rustcorp.com.au>
>
> These are obsolete: cpu_*_mask provides (const) pointers.
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> ---
This one should be preceded by a cleanup patch in ia64.
I will revise the one I posted at https://lkml.org/lkml/2012/2/14/355
and post it soon. And then you can include my patch in your patchset...
Other than that, this looks fine.
Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Regards,
Srivatsa S. Bhat
prev parent reply other threads:[~2012-02-15 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 4:58 [PATCH 12/12] cpumask: remove old cpu_*_map Rusty Russell
2012-02-15 9:36 ` Srivatsa S. Bhat [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=4F3B7C80.2080802@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=venki@google.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