From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
nhorman@tuxdriver.com, Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, oleg@redhat.com,
linuxppc-dev@ozlabs.org, mingo@redhat.com, tglx@linutronix.de,
marcin.slusarz@gmail.com, hpa@zytor.com,
Paul Mackerras <paulus@samba.org>,
akpm@linux-foundation.org, James Morris <jmorris@namei.org>,
torvalds@linux-foundation.org, mingo@elte.hu
Subject: Re: [PATCH v3 16/27] PPC: use helpers for rlimits
Date: Sun, 29 Nov 2009 22:06:03 +1100 [thread overview]
Message-ID: <20091129220603.e96d1613.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1259442963.2076.17.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
Hi Ben,
On Sun, 29 Nov 2009 08:16:03 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> On Sat, 2009-11-28 at 09:47 +0100, Jiri Slaby wrote:
> > Are you sure? The previous version with ACCESS_ONCE was generally
> > NACKed. This one uses a newly added helper which is much more cleaner
> > way to do it.
>
> I haven't seen a nack, but then I haven't pushed out yet so I can easily
> back it off and replace it with this one.
You need to hold off adding this to your tree until after patch 14/27
("resource: add helpers for fetching rlimits") of this series (or a
modified version of it) reaches Linus' tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-11-29 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1259363167-9347-1-git-send-email-jslaby@suse.cz>
2009-11-27 23:05 ` [PATCH v3 16/27] PPC: use helpers for rlimits Jiri Slaby
2009-11-28 0:19 ` Benjamin Herrenschmidt
2009-11-28 8:47 ` Jiri Slaby
2009-11-28 21:16 ` Benjamin Herrenschmidt
2009-11-29 11:06 ` Stephen Rothwell [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=20091129220603.e96d1613.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jirislaby@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=marcin.slusarz@gmail.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).