[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <zyao5vbhjt6o5duickgtgknou7j5nalyfa3nezgga7qzmmzkva@v7cbkag6yxm3>
Date: Fri, 21 Mar 2025 21:58:55 +0900
From: Koichiro Den <koichiro.den@...onical.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: linux-gpio@...r.kernel.org, geert+renesas@...der.be,
linus.walleij@...aro.org, maciej.borzecki@...onical.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 3/9] gpio: aggregator: add aggr_alloc()/aggr_free()
On Fri, Mar 21, 2025 at 01:45:45PM GMT, Bartosz Golaszewski wrote:
> On Fri, Mar 21, 2025 at 1:41 PM Koichiro Den <koichiro.den@...onical.com> wrote:
> >
> > > >
> > > > Thanks for the review. Should I send v7 for this change?
> > > >
> > >
> > > You should send one anyway once v6.15-rc1 is tagged.
> >
> > Alright. Please let me confirm:
> > - After gpio-updates-for-v6.15-rc1, will something like
> > gpio-updates-for-v6.15-rc2 follow?
>
> No. I'm not sure if I made myself clear. This series *will not* make
> v6.15. The merge window for v6.15 starts next week. I'll send my PR
> tagged as gpio-updates-for-v6.15-rc1 during the merge window. Once
> it's closed, Linus will tag v6.15-rc1 and we'll start a new
> development cycle gathering patches for v6.16 in my gpio/for-next
> branch. This is where your series will go and I'll send it upstream
> for v6.16.
Alright, that makes sense.
>
> Only send v7 in three weeks, after Linus tags RC1.
>
> > - If yes, after v6.15-rc1 is tagged, I'll _quickly_ send v7 rebased onto
> > gpio-updates-for-v6.15-rc1, right?
> >
>
> No, you'll send your series rebases on top of v6.15-rc1 tag from
> Torvalds' master branch.
Alright, thank you!
Koichiro
>
> Bart
Powered by blists - more mailing lists