From: Tero Kristo <kristo@kernel.org>
To: Suman Anna <s-anna@ti.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: Deepak Saxena <dsaxena@plexity.net>, Keerthy <j-keerthy@ti.com>,
Gowtham Tammana <g-tammana@ti.com>,
Vaibhav Gupta <v_gupta@ti.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Misc. SA2UL fixes/cleanups
Date: Mon, 17 May 2021 09:09:31 +0300 [thread overview]
Message-ID: <e28bebf5-0701-797c-414a-b18855dda624@kernel.org> (raw)
In-Reply-To: <20210514161246.22517-1-s-anna@ti.com>
On 14/05/2021 19:12, Suman Anna wrote:
> Hi All,
>
> The following series includes various fixes for multiple minor
> cleanup issues on failure paths in the TI K3 SA2UL Crypto driver.
> The patches are all based on top of 5.13-rc1.
>
> Patch 1 is the only non SA2UL patch, and allows the OMAP RNG driver
> to be built for K3 platforms and probed properly when SA2UL is
> selected, and the SA2UL driver is probed (the rng device is a child
> of the sa2ul device).
>
> regards
> Suman
>
> Suman Anna (6):
> hwrng: omap - Enable driver for TI K3 family
> crypto: sa2ul - Fix leaks on failure paths with sa_dma_init()
> crypto: sa2ul - Fix pm_runtime enable in sa_ul_probe()
> crypto: sa2ul - Use of_device_get_match_data() helper
> crypto: sa2ul - Use devm_platform_ioremap_resource()
> crypto: sa2ul - Remove child devices in remove
For the whole series:
Reviewed-by: Tero Kristo <kristo@kernel.org>
>
> drivers/char/hw_random/Kconfig | 2 +-
> drivers/crypto/sa2ul.c | 46 ++++++++++++++++++----------------
> 2 files changed, 25 insertions(+), 23 deletions(-)
>
next prev parent reply other threads:[~2021-05-17 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 16:12 [PATCH 0/6] Misc. SA2UL fixes/cleanups Suman Anna
2021-05-14 16:12 ` [PATCH 1/6] hwrng: omap - Enable driver for TI K3 family Suman Anna
2021-05-14 16:12 ` [PATCH 2/6] crypto: sa2ul - Fix leaks on failure paths with sa_dma_init() Suman Anna
2021-05-14 16:12 ` [PATCH 3/6] crypto: sa2ul - Fix pm_runtime enable in sa_ul_probe() Suman Anna
2021-05-14 16:12 ` [PATCH 4/6] crypto: sa2ul - Use of_device_get_match_data() helper Suman Anna
2021-05-14 16:12 ` [PATCH 5/6] crypto: sa2ul - Use devm_platform_ioremap_resource() Suman Anna
2021-05-14 16:12 ` [PATCH 6/6] crypto: sa2ul - Remove child devices in remove Suman Anna
2021-05-17 6:09 ` Tero Kristo [this message]
2021-05-21 8:23 ` [PATCH 0/6] Misc. SA2UL fixes/cleanups 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=e28bebf5-0701-797c-414a-b18855dda624@kernel.org \
--to=kristo@kernel.org \
--cc=davem@davemloft.net \
--cc=dsaxena@plexity.net \
--cc=g-tammana@ti.com \
--cc=herbert@gondor.apana.org.au \
--cc=j-keerthy@ti.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s-anna@ti.com \
--cc=v_gupta@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.