From: Michael Ellerman <mpe@ellerman.id.au>
To: Scott Wood <scott.wood@nxp.com>,
Horia Ioan Geanta Neag <horia.geanta@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Cristian Stoica <cristian.stoica@nxp.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Tudor-Dan Ambarus <tudor-dan.ambarus@nxp.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"David S. Miller" <davem@davemloft.net>,
Alexandru Porosanu <alexandru.porosanu@nxp.com>
Subject: Re: [PATCH v2 4/8] powerpc: add io{read,write}64 accessors
Date: Wed, 11 May 2016 10:35:04 +1000 [thread overview]
Message-ID: <1462926904.10184.2.camel@ellerman.id.au> (raw)
In-Reply-To: <DB5PR0401MB1928B01F60FF3137118F237891710@DB5PR0401MB1928.eurprd04.prod.outlook.com>
On Tue, 2016-05-10 at 18:50 +0000, Scott Wood wrote:
> On 05/09/2016 03:20 AM, Horia Ioan Geanta Neag wrote:
> > On 5/5/2016 6:37 PM, Horia Geantă wrote:
> > > This will allow device drivers to consistently use io{read,write}XX
> > > also for 64-bit accesses.
> > >
> > > Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
> >
> > It would be great if PPC maintainers could Ack this patch.
> >
> > As stated in the cover letter: https://lkml.org/lkml/2016/5/5/340
> > I'd like to go with the whole patch set via cryptodev-2.6 tree.
>
> It looks good to me. Michael?
I didn't get the cover letter, or any of the rest of the series, so although I
saw the patch I had no context. And I didn't have time to chase it up.
At a glance it seems fine, so:
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
cheers
prev parent reply other threads:[~2016-05-11 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1462462435-27403-1-git-send-email-horia.geanta@nxp.com>
2016-05-05 15:36 ` [PATCH v2 4/8] powerpc: add io{read,write}64 accessors Horia Geantă
2016-05-09 8:20 ` Horia Ioan Geanta Neag
2016-05-10 18:50 ` Scott Wood
2016-05-11 0:35 ` Michael Ellerman [this message]
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=1462926904.10184.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=alexandru.porosanu@nxp.com \
--cc=benh@kernel.crashing.org \
--cc=cristian.stoica@nxp.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=scott.wood@nxp.com \
--cc=tudor-dan.ambarus@nxp.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).