From: Eric Paris <eparis@redhat.com>
To: Will Drewry <wad@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: linux-next: build failure after merge of the final tree (security tree related)
Date: Mon, 16 Apr 2012 11:34:21 -0400 [thread overview]
Message-ID: <1334590461.2250.0.camel@localhost> (raw)
In-Reply-To: <CABqD9hauxzd4vVbxyC5M1p9e6mLt1cjYP7wbhzTKPi3iMpc0kg@mail.gmail.com>
On Mon, 2012-04-16 at 10:32 -0500, Will Drewry wrote:
> Thanks for this, and the other two fixes! I'll pull together a patch
> fixing up the other call sites. My past revisions had avoided this by
> using a new symbol, and I totally forgot to touch these up in the last
> round.
>
> What's the best way to submit the clean up -- against the security-next tree?
>
> Thanks and sorry for the noise!
Just send fixes to James and they will get picked up by Stephen the day
after he commits them to security-next.
-Eric
next prev parent reply other threads:[~2012-04-16 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 5:46 linux-next: build failure after merge of the final tree (security tree related) Stephen Rothwell
2012-04-16 15:32 ` Will Drewry
2012-04-16 15:34 ` Eric Paris [this message]
2012-04-16 15:44 ` Will Drewry
2012-04-16 16:15 ` Will Drewry
2012-04-17 1:33 ` James Morris
2012-04-17 2:02 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 7:07 Stephen Rothwell
2011-10-14 7:25 ` Sakkinen, Jarkko
2011-09-15 7:07 Stephen Rothwell
2011-09-15 22:03 ` Mimi Zohar
2011-09-16 0:51 ` James Morris
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=1334590461.2250.0.camel@localhost \
--to=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wad@chromium.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 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.