[PATCH v15 3/3] clk: aspeed: add AST2700 clock driver

[Ryan Chen]

> Subject: Re: [PATCH v15 3/3] clk: aspeed: add AST2700 clock driver
> 
> Hi Ryan,
> 
> On Mon, Oct 27, 2025 at 06:24:59AM +0000, Ryan Chen wrote:
> > Hello Stephen,
> > 	Will this be accepted in clk-next?
> 
> Given that aspeed is a SoC vendor, and you already have multiple clk drivers, I
> think at this point your best bet is to do what the other SoC vendors currently
> do. I think you should:
> 
> - Create a new subdirectory drivers/clk/aspeed/
> - Move the existing aspeed clk drivers into this subdirectory, and
>   update the Makefiles / Kconfigs as appropriate.
> - Add a new entry to the MAINTAINERS file for the aspeed clk drivers.
>   You probably also want to have that entry cover the reset driver,
>   and any other aspeed-specific drivers as well.
> - Post that patch set. Include this new clk driver as a separate patch
>   in that series. Feel free to CC me to the series and I'll review it
>   for you.
> - After it's reviewed, wait a week or two, and send Stephen a
>   'GIT PULL' using git request-pull. I can help you with the workflow
>   if needed.
> 
>   One important detail is that you want to base your branch for the GIT
>   PULL on the lowest common denominator, which is usually the latest rc1
>   from Linus. So even if Linus is at rc5, try to base yours on rc1, unless
>   there's some issue, and you need to document why. Stephen should get the
>   merge to newer rcX branches from Linus, and not you.
> 
> When you send a PULL to Stephen, you can use 'b4 am' to assemble the
> contents of your branch. When I sent him a PULL a few months ago, I included
> the b4 commands that I used.
> 
> https://lore.kernel.org/all/aL8MXYrR5uoBa4cB@x1/
> 
> If he accepts the pull, you'll still need to post your patches to the clk mailinglist,
> and have them reviewed on list. Folks from aspeed should do that review
> publicly on the list.
> 
Hello Brian,
	Thanks a lot for your guidance. I send out v16 next.
Ryan