From: Herbert Xu <herbert@gondor.apana.org.au>
To: Alexey Romanov <avromanov@salutedevices.com>
Cc: narmstrong@baylibre.com, neil.armstrong@linaro.org,
olivia@selenic.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
conor@kernel.org, khilman@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, f.fainelli@gmail.com,
hkallweit1@gmail.com, lists@kaiser.cx,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-crypto@vger.kernel.org,
kernel@sberdevices.ru, Alexey Romanov <avromanov@sberdevices.ru>
Subject: Re: [PATCH v3 1/3] drivers: rng: meson: add support for S4
Date: Wed, 20 Sep 2023 12:55:33 +0800 [thread overview]
Message-ID: <ZQp7Rf3qzoN6c2Le@gondor.apana.org.au> (raw)
In-Reply-To: <20230911101129.10604-2-avromanov@salutedevices.com>
On Mon, Sep 11, 2023 at 01:11:27PM +0300, Alexey Romanov wrote:
>
> +struct meson_rng_priv {
> + int (*read)(struct hwrng *rng, void *buf, size_t max, bool wait);
> +};
>
> struct meson_rng_data {
> void __iomem *base;
> struct hwrng rng;
> + struct device *dev;
> + const struct meson_rng_priv *priv;
> };
Is data->priv really necessary? It doesn't seem to be used anywhere
after the probe.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-09-20 4:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 10:11 [PATCH v3 0/3] Meson S4 HW RNG Support Alexey Romanov
2023-09-11 10:11 ` [PATCH v3 1/3] drivers: rng: meson: add support for S4 Alexey Romanov
2023-09-20 4:55 ` Herbert Xu [this message]
2023-09-22 8:15 ` Alexey Romanov
2023-09-26 3:15 ` Herbert Xu
2023-09-11 10:11 ` [PATCH v3 2/3] dt-bindings: rng: meson: add meson-rng-s4 compatible Alexey Romanov
2023-09-11 10:11 ` [PATCH v3 3/3] arch/arm64: dts: meson-s4: add hwrng node Alexey Romanov
2023-09-11 10:33 ` neil.armstrong
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=ZQp7Rf3qzoN6c2Le@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=avromanov@salutedevices.com \
--cc=avromanov@sberdevices.ru \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@kaiser.cx \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=olivia@selenic.com \
--cc=robh+dt@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