linux-kernel - Re: [PATCH v7 0/2] Add TI TPS65214 PMIC GPIO Support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMRc=Me7ade2aSJhn4tEAdNUvB3Y5TRLp8j8w8zgP5J3C6_MkQ@mail.gmail.com>
Date: Tue, 22 Jul 2025 16:31:08 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Jon Cormier <jcormier@...ticallink.com>
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 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.

Bartosz