[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADL8D3Zw9L+UABmSGdZio_Bq1Nx5tJ226EFtVY6DT3xgYBs92w@mail.gmail.com>
Date: Tue, 22 Jul 2025 10:32:40 -0400
From: Jon Cormier <jcormier@...ticallink.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Shree Ramamoorthy <s-ramamoorthy@...com>, aaro.koskinen@....fi, andreas@...nade.info,
khilman@...libre.com, rogerq@...nel.org, tony@...mide.com,
linus.walleij@...aro.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org, m-leonard@...com,
praneeth@...com, christophe.jaillet@...adoo.fr
Subject: Re: [PATCH v7 0/2] Add TI TPS65214 PMIC GPIO Support
On Tue, Jul 22, 2025 at 10:31 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> On Tue, Jul 22, 2025 at 4:16 PM Jon Cormier <jcormier@...ticallink.com> wrote:
> > >
> > > This doesn't apply on top of my gpio/for-next branch. Do you think you
> > > can quickly submit another iteration rebased on top of it?
> > Maybe this is a basic question but is there a rule of thumb for where
> > to base patches to be submitted to the mailing lists? I've generally
> > been basing them off the latest tag in linux-stable/master. I suppose
> > this might be one of those it depends on the subsystem things?
> > >
>
> I feed my tree into linux next, so generally using linux-next/master
> would be your best bet. The rule of thumb typically is checking the
> subsystem's git tree in MAINTAINERS and using whatever branch goes
> into the next release.
Awesome, thanks for the info!
>
> Bartosz
--
Jonathan Cormier
Senior Software Engineer
Voice: 315.425.4045 x222
http://www.CriticalLink.com
6712 Brooklawn Parkway, Syracuse, NY 13211
Powered by blists - more mailing lists