From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Jon Cormier <jcormier@criticallink.com>
Cc: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
aaro.koskinen@iki.fi, andreas@kemnade.info,
khilman@baylibre.com, rogerq@kernel.org, tony@atomide.com,
linus.walleij@linaro.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
m-leonard@ti.com, praneeth@ti.com,
christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v7 0/2] Add TI TPS65214 PMIC GPIO Support
Date: Tue, 22 Jul 2025 16:31:08 +0200 [thread overview]
Message-ID: <CAMRc=Me7ade2aSJhn4tEAdNUvB3Y5TRLp8j8w8zgP5J3C6_MkQ@mail.gmail.com> (raw)
In-Reply-To: <CADL8D3YaF4zt2Wu0Vv1=8W9e9n5BKM+2npgfVmLhJ=wz-jHMKQ@mail.gmail.com>
On Tue, Jul 22, 2025 at 4:16 PM Jon Cormier <jcormier@criticallink.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
next prev parent reply other threads:[~2025-07-22 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 23:31 [PATCH v7 0/2] Add TI TPS65214 PMIC GPIO Support Shree Ramamoorthy
2025-07-21 23:31 ` [PATCH v7 1/2] gpio: tps65219: Update _IDX & _OFFSET macro prefix Shree Ramamoorthy
2025-07-21 23:31 ` [PATCH v7 2/2] gpio: tps65219: Add support for TI TPS65214 PMIC Shree Ramamoorthy
2025-07-22 12:33 ` [PATCH v7 0/2] Add TI TPS65214 PMIC GPIO Support Bartosz Golaszewski
2025-07-22 14:16 ` Jon Cormier
2025-07-22 14:31 ` Bartosz Golaszewski [this message]
2025-07-22 14:32 ` Jon Cormier
2025-07-22 15:23 ` Shree Ramamoorthy
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='CAMRc=Me7ade2aSJhn4tEAdNUvB3Y5TRLp8j8w8zgP5J3C6_MkQ@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jcormier@criticallink.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).