public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Paris <eparis@redhat.com>
Cc: James Morris <jmorris@namei.org>, linux-next@vger.kernel.org
Subject: Re: linux-next: security-testing tree build failure
Date: Sat, 15 Nov 2008 12:56:16 +1100	[thread overview]
Message-ID: <20081115125616.c9324345.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1226702522.3353.85.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

Hi Eric,

On Fri, 14 Nov 2008 17:42:02 -0500 Eric Paris <eparis@redhat.com> wrote:
>
> I am aware.  James didn't like my first fix for CONFIG_AUDIT but not
> CONFIG_SECURITY_FILE_CAPABILITIES so I just sent another one which
> should address the concern.

Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-11-15  1:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13  7:46 linux-next: security-testing tree build failure Stephen Rothwell
2008-11-14  7:43 ` Stephen Rothwell
2008-11-14 22:42   ` Eric Paris
2008-11-15  1:56     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-07 13:40 Stephen Rothwell
2009-09-07 13:43 ` Stephen Rothwell
2009-09-08  0:40   ` Stephen Rothwell
2009-09-08  3:22     ` Stephen Rothwell
2009-09-07 10:38 Stephen Rothwell
2009-09-03  5:51 Stephen Rothwell
2009-08-07  4:59 Stephen Rothwell
2009-08-10 14:07 ` Eric Paris
2009-08-10 23:58   ` Stephen Rothwell
2009-02-06  7:28 Stephen Rothwell
2009-02-06  8:14 ` James Morris
2008-11-12  5:05 Stephen Rothwell
2008-11-12 10:56 ` James Morris
2008-11-12 14:05   ` Eric Paris

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=20081115125616.c9324345.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=eparis@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-next@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