All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Holland <samuel@sholland.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>,
	Lukasz Majewski <lukma@denx.de>,
	Sean Anderson <seanga2@gmail.com>, Bin Meng <bmeng.cn@gmail.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH 0/7] clk: sunxi: Out-of-bounds access fix and driver cleanup
Date: Mon, 27 Jun 2022 21:45:16 -0500	[thread overview]
Message-ID: <b2169b42-644b-cae4-6320-f0b7d897f18f@sholland.org> (raw)
In-Reply-To: <20220628014029.26d54014@slackpad.lan>

Hi Andre,

On 6/27/22 7:40 PM, Andre Przywara wrote:
> On Mon,  9 May 2022 00:29:30 -0500
> Samuel Holland <samuel@sholland.org> wrote:
> 
> Hi Samuel,
> 
>> This series fixes an issue with out-of-bounds access to the gate array
>> (patches 1-2), uses the rearranged array size information to remove a
>> bunch of duplicate code (patches 3-4), and then simplifies how the reset
>> driver is bound (patches 5-7).
>>
>> The original motivation for these changes was adding a driver for the
>> legacy A31/A23/A33 PRCM binding (which I will send separately), and
>> trying to use OF_PLATDATA in SPL (which did not work out). But I think
>> at least some of the cleanup is worth applying on its own.
>>
>> Patch 4 is generally the same change I made between v1 and v2 of the
>> pinctrl series, using some #ifdefs to share a U_BOOT_DRIVER. It's not
>> quite as clean as the pinctrl case, because here the SoC-specific parts
>> are in different files, so all of the CCU descriptors have to be global.
> 
> Many thanks for your work on this!
> So I am done with reviewing this series, and as mentioned quite like it
> and am fine with it. I added F1C100s support, which got added in U-Boot
> meanwhile, and pushed that to sunxi/next:
> https://source.denx.de/u-boot/custodians/u-boot-sunxi/-/commits/next/
> 
> Can you please have a look and confirm that this is fine? I will then
> send the PR in about two weeks time, if nothing breaks.

Looks good to me, and thanks for taking care of F1C100s. My only trivial comment
is that you left out Sean's ack.

Regards,
Samuel

      reply	other threads:[~2022-06-28  2:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  5:29 [PATCH 0/7] clk: sunxi: Out-of-bounds access fix and driver cleanup Samuel Holland
2022-05-09  5:29 ` [PATCH 1/7] clk: sunxi: Store the array sizes in the CCU descriptor Samuel Holland
2022-06-25 17:10   ` Andre Przywara
2022-05-09  5:29 ` [PATCH 2/7] clk: sunxi: Prevent out-of-bounds gate array access Samuel Holland
2022-06-26 10:43   ` Andre Przywara
2022-05-09  5:29 ` [PATCH 3/7] reset: sunxi: Get the reset count from the CCU descriptor Samuel Holland
2022-06-26 10:51   ` Andre Przywara
2022-05-09  5:29 ` [PATCH 4/7] clk: sunxi: Use a single driver for all variants Samuel Holland
2022-06-27  0:43   ` Andre Przywara
2022-05-09  5:29 ` [PATCH 5/7] clk: sunxi: Convert driver private data to platform data Samuel Holland
2022-06-27 19:34   ` Andre Przywara
2022-05-09  5:29 ` [PATCH 6/7] reset: " Samuel Holland
2022-06-27 19:41   ` Andre Przywara
2022-05-09  5:29 ` [PATCH 7/7] reset: sunxi: Reuse the platform data from the clock driver Samuel Holland
2022-06-27 23:45   ` Andre Przywara
2022-05-10 23:24 ` [PATCH 0/7] clk: sunxi: Out-of-bounds access fix and driver cleanup Andre Przywara
2022-05-11 15:48 ` Sean Anderson
2022-06-28  0:40 ` Andre Przywara
2022-06-28  2:45   ` Samuel Holland [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=b2169b42-644b-cae4-6320-f0b7d897f18f@sholland.org \
    --to=samuel@sholland.org \
    --cc=andre.przywara@arm.com \
    --cc=bmeng.cn@gmail.com \
    --cc=jagan@amarulasolutions.com \
    --cc=lukma@denx.de \
    --cc=mripard@kernel.org \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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.