From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: mpm@selenic.com, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] hwrng: amd: Rework of the amd768-hwrng driver
Date: Fri, 26 Aug 2016 10:38:02 +0200 [thread overview]
Message-ID: <20160826083802.GA32290@Red> (raw)
In-Reply-To: <20160825145638.GD10637@io.lakedaemon.net>
On Thu, Aug 25, 2016 at 02:56:38PM +0000, Jason Cooper wrote:
> Hi Corentin,
>
> On Thu, Aug 25, 2016 at 02:16:35PM +0200, LABBE Corentin wrote:
> > This patch convert the hwrng interface used by amd768-rng to its new API
> > by replacing data_read()/data_present() by read().
> >
> > Furthermore, Instead of having two global variable, it's better to use a
> > private struct. This will permit to remove amd_pdev variable.
> >
> > Finally, Instead of accessing hw directly via pmbase, it's better to
> > access after ioport_map() via ioread32/iowrite32.
>
> I was going to recommend a better $subject line, but now I see why it's
> vague. :( I would recommend breaking this patch up into three:
>
> hwrng: amd - Access hardware via ioread32/iowrite32
> hwrng: amd - Replace global variable with private struct
> hwrng: amd - Convert to new hwrng read() API
>
That was my first idea, but believed that it wasnt worth it.
Anyway I will do it.
Regards
LABBE Corentin
next prev parent reply other threads:[~2016-08-26 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 12:16 [PATCH v2 0/5] hwrng: amd: rework of the amd hwrng driver LABBE Corentin
2016-08-25 12:16 ` [PATCH v2 1/5] hwrng: amd: Fix style problem with blank line LABBE Corentin
2016-08-25 12:16 ` [PATCH v2 2/5] hwrng: amd: use the BIT macro LABBE Corentin
2016-08-25 12:16 ` [PATCH v2 3/5] hwrng: amd: Be consitent with the driver name LABBE Corentin
2016-08-25 12:16 ` [PATCH v2 4/5] hwrng: amd: Remove asm/io.h LABBE Corentin
2016-08-25 12:16 ` [PATCH v2 5/5] hwrng: amd: Rework of the amd768-hwrng driver LABBE Corentin
2016-08-25 14:56 ` Jason Cooper
2016-08-26 8:38 ` LABBE Corentin [this message]
2016-08-26 13:29 ` Jason Cooper
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=20160826083802.GA32290@Red \
--to=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jason@lakedaemon.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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