The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: James Morris <jmorris@namei.org>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [AppArmor 0/3] Cleanups to AppArmor's build
Date: Tue, 08 Mar 2011 17:27:33 -0800	[thread overview]
Message-ID: <4D76D785.8060408@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1103091025130.28443@tundra.namei.org>

On 03/08/2011 03:32 PM, James Morris wrote:
> On Tue, 8 Mar 2011, John Johansen wrote:
> 
>> The following three patches have all been out to the lkml/lsm and have sat in
>> the AppArmor tree for a while.
>>
>> The following changes since commit eae61f3c829439f8f9121b5cd48a14be04df451f:
>>
>>   TOMOYO: Fix memory leak upon file open. (2011-03-03 10:13:26 +1100)
>>
>> are available in the git repository at:
>>   git://git.kernel.org/pub/scm/linux/kernel/git/jj/apparmor-dev.git security-next
>>
>> John Johansen (3):
>>       AppArmor: Cleanup make file to remove cruft and make it easier to read
>>       AppArmor: cleanup generated files correctly
>>       AppArmor: kill unused macros in lsm.c
> 
> These patches are showing up here with you as the author (not the original 
> authors).  If applying raw patches, you'll need to set GIT_AUTHOR_EMAIL 
> and GIT_AUTHOR_NAME, or more simply, use git-am -s on mailbox format files 
> exported from your mailer.
> 
Ah yep sorry about that, I've reimported and pushed it up.

The following changes since commit eae61f3c829439f8f9121b5cd48a14be04df451f:

  TOMOYO: Fix memory leak upon file open. (2011-03-03 10:13:26 +1100)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/jj/apparmor-dev.git security-next

John Johansen (1):
      AppArmor: Cleanup make file to remove cruft and make it easier to read

Michal Hocko (1):
      AppArmor: cleanup generated files correctly

Shan Wei (1):
      AppArmor: kill unused macros in lsm.c

 security/apparmor/Makefile |   38 +++++++++++++++++++++++++++++++++-----
 security/apparmor/lsm.c    |    2 --
 2 files changed, 33 insertions(+), 7 deletions(-)

  reply	other threads:[~2011-03-09  1:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 19:03 [AppArmor 0/3] Cleanups to AppArmor's build John Johansen
2011-03-08 19:03 ` [PATCH 1/3] AppArmor: Cleanup make file to remove cruft and make it easier to read John Johansen
2011-03-08 19:03 ` [PATCH 2/3] AppArmor: cleanup generated files correctly John Johansen
2011-03-08 19:03 ` [PATCH 3/3] AppArmor: kill unused macros in lsm.c John Johansen
2011-03-08 23:32 ` [AppArmor 0/3] Cleanups to AppArmor's build James Morris
2011-03-09  1:27   ` John Johansen [this message]
2011-03-09  3:14     ` 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=4D76D785.8060408@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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