From: David Miller <davem@davemloft.net>
To: matorola@gmail.com
Cc: linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org,
herbert@gondor.apana.org.au
Subject: Re: [PATCH 0/2] n2rng: Attach on T5/M5, T7/M7 SPARC CPUs
Date: Fri, 15 Jan 2016 15:22:53 -0500 (EST) [thread overview]
Message-ID: <20160115.152253.1613974535141140248.davem@davemloft.net> (raw)
In-Reply-To: <20160113214318.GB32766@yogzotot>
From: Anatoly Pugachev <matorola@gmail.com>
Date: Thu, 14 Jan 2016 00:43:18 +0300
> This patch adds support for recent oracle hardware (T5/M5, T7/M7 SPARC CPUs),
> so n2_rng driver would work on them.
>
> 1. n2rng: Attach on T5/M5, T7/M7 SPARC CPUs
> 2. n2rng: documentation, add DT bindings, vendor prefixes
>
> PS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809815#32
>
> Signed-off-by: Anatoly Pugachev <matorola@gmail.com>
This series looks fine:
Acked-by: David S. Miller <davem@davemloft.net>
Herbert, please take this via your crypto tree.
Thanks!
next prev parent reply other threads:[~2016-01-15 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 21:43 [PATCH 0/2] n2rng: Attach on T5/M5, T7/M7 SPARC CPUs Anatoly Pugachev
2016-01-15 20:22 ` David Miller [this message]
2016-01-25 14:41 ` Herbert Xu
2016-01-25 16:13 ` Anatoly Pugachev
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=20160115.152253.1613974535141140248.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=sparclinux@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