Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: alastair@au1.ibm.com, linux-kernel@vger.kernel.org,
	paulus@samba.org, linux-crypto@vger.kernel.org,
	Alastair D'Silva <alastair@d-silva.org>,
	linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH 0/2] Automatically load the vmx_crypto module if supported
Date: Tue, 19 Jul 2016 19:13:24 +1000	[thread overview]
Message-ID: <10065.6168106527$1468919680@news.gmane.org> (raw)
In-Reply-To: <20160719035939.GA20847@gondor.apana.org.au>

Herbert Xu <herbert@gondor.apana.org.au> writes:

> On Tue, Jul 19, 2016 at 11:01:55AM +1000, Michael Ellerman wrote:
>>
>> Can you please ask for an ack before merging arch patches?
>> 
>> That's a 70 line powerpc patch and a 6 line crypto patch. It has no
>> reviews and no acks. I would have preferred it if we could take it via
>> the powerpc tree.
>
> Sorry, I'll delete them from the crypto tree.

Thanks.

I'll assume patch 2 has your ack :)

cheers
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

  parent reply	other threads:[~2016-07-19  9:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13  5:47 [PATCH 0/2] Automatically load the vmx_crypto module if supported alastair
2016-07-13  5:47 ` [PATCH 1/2] Allow drivers to be autoloaded alastair
2016-07-13  5:47 ` [PATCH 1/2] powerpc: Add module autoloading based on CPU features alastair
2016-07-19  1:04   ` Michael Ellerman
2016-07-19  1:04   ` Michael Ellerman
2016-07-13  5:47 ` [PATCH 2/2] Automatically load the vmx_crypto module if supported alastair
2016-07-13  5:47 ` [PATCH 2/2] crypto: vmx - Convert to CPU feature based module autoloading alastair
2016-07-13  5:54 ` [PATCH 0/2] Automatically load the vmx_crypto module if supported Alastair D'Silva
2016-07-14  3:34   ` Balbir Singh
2016-07-18 10:22 ` Herbert Xu
2016-07-19  1:01   ` Michael Ellerman
2016-07-19  1:01   ` Michael Ellerman
     [not found]   ` <87fur6phj0.fsf@@concordia.ellerman.id.au>
2016-07-19  3:59     ` Herbert Xu
2016-07-19  9:13       ` Michael Ellerman
2016-07-19  9:13       ` Michael Ellerman [this message]
     [not found]       ` <87poqa9eiz.fsf@@concordia.ellerman.id.au>
2016-07-19  9:52         ` Herbert Xu

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='10065.6168106527$1468919680@news.gmane.org' \
    --to=mpe@ellerman.id.au \
    --cc=alastair@au1.ibm.com \
    --cc=alastair@d-silva.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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