From: Paul Moore <paul.moore@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-audit@redhat.com
Subject: Re: [PATCH] One more XFRM audit fix
Date: Thu, 20 Dec 2007 07:25:03 -0500 [thread overview]
Message-ID: <200712200725.03888.paul.moore@hp.com> (raw)
In-Reply-To: <20071220.000009.173158004.davem@davemloft.net>
On Thursday 20 December 2007 3:00:09 am David Miller wrote:
> From: Paul Moore <paul.moore@hp.com>
> Date: Wed, 19 Dec 2007 14:29:31 -0500
>
> > The following patch is backed against David's net-2.6 tree and is pretty
> > trivial. I know we're late in the 2.6.24 cycle but I think this is worth
> > merging, if you guys don't feel that way let me know and I'll resubmit it
> > for 2.6.25.
>
> Where is that patch? Or do you mean the fix you emailed
> seperately today (which I will apply, thanks)?
Yes, it was the patch you applied, "XFRM: Audit function arguments
misordered". I was using stacked-git to post the patch and it apparently
doesn't annotate the cover email's subject line with "0/1" when you only send
one patch.
Sorry about that.
> > As a side note, I'm unable to actually test the patch because I can't get
> > the kernel to compile (M=net/xfrm works just fine). The problem I keep
> > seeing is below:
> >
> > make[3]: *** No rule to make target \
> > `/blah/kernels/net-2.6_xfrm-auid-secid-fix/include/linux/ticable.h', \
> > needed by \
> > `/blah/kernels/net-2.6_xfrm-auid-secid-fix/usr/include/linux/ticable.h'.
> > \ Stop.
>
> Remove ticable.h from include/linux/Kbuild
>
> This is already cured in Linus's tree.
Noted, thanks.
--
paul moore
linux security @ hp
prev parent reply other threads:[~2007-12-20 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 19:29 [PATCH] One more XFRM audit fix Paul Moore
2007-12-19 19:29 ` [PATCH] XFRM: Audit function arguments misordered Paul Moore
2007-12-20 8:01 ` David Miller
2007-12-20 8:00 ` [PATCH] One more XFRM audit fix David Miller
2007-12-20 12:25 ` Paul Moore [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=200712200725.03888.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=davem@davemloft.net \
--cc=linux-audit@redhat.com \
--cc=netdev@vger.kernel.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).