public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: James Morris <jmorris@namei.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the security-testing tree
Date: Fri, 30 Jul 2010 00:31:37 -0700	[thread overview]
Message-ID: <4C527FD9.3060708@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1007301353340.8846@tundra.namei.org>

On 07/29/2010 08:54 PM, James Morris wrote:
> On Fri, 30 Jul 2010, Stephen Rothwell wrote:
> 
>> Hi James,
>>
>> After merging the security-testing tree, today's linux-next build
>> (powerpc ppc64_defconfig) failed like this:
>>
>> security/Kconfig:144: can't open file "security/apparmor/Kconfig"
>>
>> Caused by commit 32bd8e5273c0be4189274ab55c4d16862f0dd87d ("AppArmor:
>> Enable configuring and building of the AppArmor security module").  Looks
>> like a file was missed.
> 
> I don't know how to use git.
> 
> Should be fixed now.
> 
works for me,

thanks James

  parent reply	other threads:[~2010-07-30  7:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30  2:06 linux-next: build failure after merge of the security-testing tree Stephen Rothwell
2010-07-30  3:54 ` James Morris
2010-07-30  6:01   ` Stephen Rothwell
2010-07-30  7:31   ` John Johansen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-02  2:16 Stephen Rothwell
2010-08-03  0:04 ` John Johansen
2010-08-05  1:37   ` Stephen Rothwell
2010-10-19  3:57 Stephen Rothwell
2010-10-19  4:09 ` Eric Paris
2011-06-29  3:48 Stephen Rothwell
2011-06-29  4:16 ` Tetsuo Handa
2011-06-29  7:36   ` James Morris
2011-08-10  0:58 Stephen Rothwell
2011-08-10  1:48 ` Mimi Zohar
2011-08-10  7:21   ` James Morris
2011-08-12  2:47 Stephen Rothwell
2011-08-15  4:04 ` Stephen Rothwell

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=4C527FD9.3060708@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.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