From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Samuel Holland <samuel@sholland.org>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v2 0/2] nvmem: sunxi_sid: Fix for D1 variant
Date: Tue, 3 Jan 2023 11:33:13 +0000 [thread overview]
Message-ID: <fc321ad7-0622-5869-d934-97baaf540c07@linaro.org> (raw)
In-Reply-To: <20230101183316.43642-1-samuel@sholland.org>
On 01/01/2023 18:33, Samuel Holland wrote:
> This is the first two patches from [1], with the stable CC added.
> The first patch fixes a bug causing incorrect values to be read; the
> second is a cleanup. I split the series since this bug needs to be
> fixed regardless of the DT binding discussion.
>
> [1]: https://lore.kernel.org/lkml/20220814173656.11856-1-samuel@sholland.org/
>
> Changes in v2:
> - Split out the driver fix from the other changes
>
> Samuel Holland (2):
> nvmem: sunxi_sid: Always use 32-bit MMIO reads
> nvmem: sunxi_sid: Drop the workaround on A64
>
Applied thanks,
--srini
> drivers/nvmem/sunxi_sid.c | 23 +++++++++++++++--------
> 1 file changed, 15 insertions(+), 8 deletions(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-03 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 18:33 [PATCH v2 0/2] nvmem: sunxi_sid: Fix for D1 variant Samuel Holland
2023-01-01 18:33 ` [PATCH v2 1/2] nvmem: sunxi_sid: Always use 32-bit MMIO reads Samuel Holland
2023-01-08 20:52 ` Jernej Škrabec
2023-01-01 18:33 ` [PATCH v2 2/2] nvmem: sunxi_sid: Drop the workaround on A64 Samuel Holland
2023-01-03 11:33 ` Srinivas Kandagatla [this message]
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=fc321ad7-0622-5869-d934-97baaf540c07@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=wens@csie.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