From: David Miller <davem@davemloft.net>
To: julia@diku.dk
Cc: peterz@infradead.org, mingo@elte.hu, tglx@linutronix.de,
oleg@redhat.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 7/7] arch/sparc/kernel: Use set_cpus_allowed_ptr
Date: Sun, 28 Mar 2010 04:12:13 +0000 [thread overview]
Message-ID: <20100327.211213.13750482.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1003262303500.6480@ask.diku.dk>
From: Julia Lawall <julia@diku.dk>
Date: Fri, 26 Mar 2010 23:04:09 +0100 (CET)
> Use set_cpus_allowed_ptr rather than set_cpus_allowed.
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
...
> Signed-off-by: Julia Lawall <julia@diku.dk>
Applied, thanks Julia.
prev parent reply other threads:[~2010-03-28 4:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 22:04 [PATCH 7/7] arch/sparc/kernel: Use set_cpus_allowed_ptr Julia Lawall
2010-03-28 4:12 ` David Miller [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=20100327.211213.13750482.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).