From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, Al Viro <viro@ZenIV.linux.org.uk>,
linux-next@vger.kernel.org, James Morris <jmorris@namei.org>,
Eric Paris <eparis@redhat.com>, Serge Hallyn <serue@us.ibm.com>
Subject: Re: linux-next: manual merge of the audit tree
Date: Wed, 10 Dec 2008 18:58:29 +0000 [thread overview]
Message-ID: <13157.1228935509@redhat.com> (raw)
In-Reply-To: <20081209175726.682d77cd.sfr@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Today's linux-next merge of the audit tree got a lot of conflict in
> include/linux/audit.h, kernel/auditsc.c, kernel/capability.c and
> security/commoncap.c against commits in the security-testing tree.
>
> Its not obvious how to resolve these, so can you, Eric, James and Dave
> have a conversation and see what you can come up with. Some will be
> easy, but there are several overlapping changes here.
>
> Looking harder, it looks like some (all?) of Eric's patches may already
> be in the security-testing tree ...
>
> I have dropped the audit tree for today.
I've looked at all the conflicting bits, and I think you should take what's in
the security tree over what's in Al's tree for all of them. I think the
security tree already has everything that Al's tree applies in the conflicting
areas, it's just that the security tree has further changes parked on top.
David
next prev parent reply other threads:[~2008-12-10 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 6:57 linux-next: manual merge of the audit tree Stephen Rothwell
2008-12-10 18:58 ` David Howells [this message]
2008-12-10 19:01 ` Eric Paris
2008-12-10 19:33 ` David Howells
2008-12-11 6:31 ` Al Viro
2008-12-11 9:01 ` Stephen Rothwell
2008-12-10 23:28 ` Al Viro
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=13157.1228935509@redhat.com \
--to=dhowells@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-next@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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).