Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: LABBE Corentin <clabbe.montjoie@gmail.com>
Cc: mpm@selenic.com, herbert@gondor.apana.org.au,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/8] hwrng: amd: Replace global variable with private struct
Date: Sat, 27 Aug 2016 15:36:15 +0000	[thread overview]
Message-ID: <20160827153615.GN10637@io.lakedaemon.net> (raw)
In-Reply-To: <20160827144331.GK10637@io.lakedaemon.net>

On Sat, Aug 27, 2016 at 02:43:31PM +0000, Jason Cooper wrote:
> Hi Corentin,
> 
> On Fri, Aug 26, 2016 at 01:11:34PM +0200, LABBE Corentin wrote:
> > Instead of having two global variable, it's better to use a
> > private struct. This will permit to remove amd_pdev variable
> > 
> > Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
> > ---
> >  drivers/char/hw_random/amd-rng.c | 57 ++++++++++++++++++++++++++--------------
> >  1 file changed, 38 insertions(+), 19 deletions(-)
> > 
> > diff --git a/drivers/char/hw_random/amd-rng.c b/drivers/char/hw_random/amd-rng.c
> > index 383e197..4ef94e9 100644
> > --- a/drivers/char/hw_random/amd-rng.c
> > +++ b/drivers/char/hw_random/amd-rng.c
> > @@ -47,15 +47,18 @@ static const struct pci_device_id pci_tbl[] = {
> >  };
> >  MODULE_DEVICE_TABLE(pci, pci_tbl);
> >  
> > -static struct pci_dev *amd_pdev;
> > +struct amd768_priv {
> > +	struct pci_dev *pcidev;
> > +	u32 pmbase;
> > +};
> >  
> >  static int amd_rng_data_present(struct hwrng *rng, int wait)
> >  {
> > -	u32 pmbase = (u32)rng->priv;
> > +	struct amd768_priv *priv = (struct amd768_priv *)rng->priv;
> 
> Please remove unnecessary casts...

Hmm, I was assuming that, like other places in the tree, that priv was
declared void*.  However, it's unsigned long in hw_random.h.

And, it looks like all users cast it.  Either to a struct, or to a void
__iomem *.

So ignore what I said in my previous email.  You can add my reviewed-by
without change.

It does look like /priv/ s/unsigned long/void */ would be a great
cleanup.

thx,

Jason.

  reply	other threads:[~2016-08-27 15:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 11:11 [PATCH v3 0/8] hwrng: amd: rework of the amd hwrng driver LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 1/8] hwrng: amd: Fix style problem with blank line LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 2/8] hwrng: amd: use the BIT macro LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 3/8] hwrng: amd: Be consitent with the driver name LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 4/8] hwrng: amd: Remove asm/io.h LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 5/8] hwrng: amd: release_region must be called after hwrng_unregister LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 6/8] hwrng: amd: Replace global variable with private struct LABBE Corentin
2016-08-27 14:43   ` Jason Cooper
2016-08-27 15:36     ` Jason Cooper [this message]
2016-08-26 11:11 ` [PATCH v3 7/8] hwrng: amd: Access hardware via ioread32/iowrite32 LABBE Corentin
2016-08-26 11:11 ` [PATCH v3 8/8] hwrng: amd: Convert to new hwrng read() API LABBE Corentin
2016-08-27 14:49 ` [PATCH v3 0/8] hwrng: amd: rework of the amd hwrng driver Jason Cooper
2016-08-31 15:18 ` 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=20160827153615.GN10637@io.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=clabbe.montjoie@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --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