linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Behan Webster <behanw@converseincode.com>
To: John Johansen <john.johansen@canonical.com>,
	agk@redhat.com, clm@fb.com, davem@davemloft.net,
	dm-devel@redhat.com, fabf@skynet.be, herbert@gondor.apana.org.au,
	jbacik@fb.com, snitzer@redhat.com
Cc: akpm@linux-foundation.org, james.l.morris@oracle.com,
	linux-btrfs@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-security-module@vger.kernel.org, neilb@suse.de,
	serge@hallyn.com, torvalds@linux-foundation.org,
	"Vinícius Tinti" <viniciustinti@gmail.com>,
	"Jan-Simon Möller" <dl9pf@gmx.de>,
	"Mark Charlebois" <charlebm@gmail.com>
Subject: Re: [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
Date: Tue, 02 Sep 2014 16:26:22 -0700	[thread overview]
Message-ID: <5406521E.9090006@converseincode.com> (raw)
In-Reply-To: <54064FD1.6060900@canonical.com>

On 09/02/14 16:16, John Johansen wrote:
>
> I'm fine with this, do you want me to pull it into my tree for our next push
> or do you want this all to go together as a set?
>
> Acked-by: John Johansen <john.johansen@canonical.com>
I'm more than happy for individual maintainers to pull relevant patches 
into their trees for the next merge window.

They were presented as a RFC patch set purely to get consensus as a 
group since its the same change across the board.

Happy to push your patch to you now.

Behan

-- 
Behan Webster
behanw@converseincode.com


  reply	other threads:[~2014-09-02 23:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 22:32 [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM behanw
2014-09-02 22:32 ` [PATCH RFC 1/6] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt behanw
2014-09-02 22:32 ` [PATCH RFC 2/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c behanw
2014-09-02 22:32 ` [PATCH RFC 3/6] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c behanw
2014-09-02 22:32 ` [PATCH RFC 4/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c behanw
2014-09-02 22:32 ` [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS behanw
2014-09-02 23:16   ` John Johansen
2014-09-02 23:26     ` Behan Webster [this message]
2014-09-02 22:32 ` [PATCH RFC 6/6] btrfs: " behanw
2014-09-02 23:01 ` [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Marcel Holtmann
2014-09-02 23:04   ` Jan-Simon Möller
2014-09-02 23:07   ` Behan Webster

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=5406521E.9090006@converseincode.com \
    --to=behanw@converseincode.com \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=charlebm@gmail.com \
    --cc=clm@fb.com \
    --cc=davem@davemloft.net \
    --cc=dl9pf@gmx.de \
    --cc=dm-devel@redhat.com \
    --cc=fabf@skynet.be \
    --cc=herbert@gondor.apana.org.au \
    --cc=james.l.morris@oracle.com \
    --cc=jbacik@fb.com \
    --cc=john.johansen@canonical.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=serge@hallyn.com \
    --cc=snitzer@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viniciustinti@gmail.com \
    /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).