From: Johan Hovold <johan@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Vignesh R <vigneshr@ti.com>, Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH] i2c: omap: fix deprecated of_property_read_bool() use
Date: Tue, 6 May 2025 09:01:46 +0200 [thread overview]
Message-ID: <aBmz2iDObAgendMc@hovoldconsulting.com> (raw)
In-Reply-To: <6nn2l75kkbkdu3wf3kta4mezno6cy4e3zzwzdc4cpmujjhr6lp@ct7w72zwbrhu>
On Tue, May 06, 2025 at 12:13:00AM +0200, Andi Shyti wrote:
> On Mon, May 05, 2025 at 12:00:07PM +0200, Johan Hovold wrote:
> > On Tue, Apr 29, 2025 at 03:10:13PM +0200, Andi Shyti wrote:
> > > I'm sorry, but as I understand it, the Fixes tag should be used
> > > only when an actual bug is being fixed. I've seen stable
> > > maintainers getting annoyed when it's used for non-bug issues.
> >
> > You seem to confuse the Fixes tag with a CC stable tag. A Fixes tag is
> > used to indicate which commit introduced an issue, while the CC stable
> > tag is used to flag a commit for backporting (and the fact that autosel
> > tends to pick up patches with just a Fixes doesn't change this).
>
> (the Cc tag for fixes is not mandatory, it's more a courtesy)
You should still add it as described by the stable tree docs:
To have a patch you submit for mainline inclusion later
automatically picked up for stable trees, add this tag in the
sign-off area::
Cc: stable@vger.kernel.org
The stable team also scans through patches with just a Fixes tag because
some people forget to add the tag, don't know that they should, or don't
care about stable, but you should not rely on that (as I alluded to
above).
> > It's perfectly fine to fix an issue and use a Fixes tag when doing so
> > even if the fix itself does not qualify for backporting (for whatever
> > reason).
>
> Oh yes, I forgot that patch was part of the 6.15 merge window. I
> will then move it to the -fixes and send it for this week's merge
> request.
Perfect, thanks.
Johan
prev parent reply other threads:[~2025-05-06 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 7:52 [PATCH] i2c: omap: fix deprecated of_property_read_bool() use Johan Hovold
2025-04-15 11:48 ` Mukesh Kumar Savaliya
2025-04-17 21:41 ` Andi Shyti
2025-04-17 22:18 ` Andi Shyti
2025-04-18 9:57 ` Johan Hovold
2025-04-29 13:10 ` Andi Shyti
2025-05-02 12:54 ` Andreas Kemnade
2025-05-05 10:00 ` Johan Hovold
2025-05-05 22:13 ` Andi Shyti
2025-05-06 7:01 ` Johan Hovold [this message]
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=aBmz2iDObAgendMc@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andi.shyti@kernel.org \
--cc=andreas@kemnade.info \
--cc=j-choudhary@ti.com \
--cc=jmkrzyszt@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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).