From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
s.shtylyov@omp.ru, linux-ide@vger.kernel.org,
linux-m68k@vger.kernel.org, will@sowerbutts.com,
rz@linux-m68k.org, geert@linux-m68k.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/3] m68k/q40: fix IO base selection for Q40 in pata_falcon.c
Date: Fri, 18 Aug 2023 15:33:29 +1000 (AEST) [thread overview]
Message-ID: <ef903aa8-25aa-779b-cf88-33840b498282@linux-m68k.org> (raw)
In-Reply-To: <a75c21bc-c776-cf19-a5b2-9163af035d65@gmail.com>
On Fri, 18 Aug 2023, Michael Schmitz wrote:
> >> Cc: <stable@vger.kernel.org> # 5.14
> >
> > 5.14+ ? But I do not think you need to specify anything anyway since
> > you have the Fixes tag.
>
> 5.14+ perhaps. I'll check the docs again to see whether Fixes: obsoletes
> the stable backport tag. I've so far used both together...
>
You'd specify a "# x.y+" limit along with a "Fixes" tag if you don't want
to backport as far back as the buggy commit (because some other
pre-requisite isn't present on the older branches). But that does not
apply in this case.
Writing "# 5.14" is surprising because (according to www.kernel.org
landing page) that branch was abandoned, and no live branch was named.
But in "git log" you can see that people write this anyway.
Writing "# 5.14+" or "# 5.15+" is clear enough but is normally omitted
when it can be inferred from the Fixes tag. That's been my experience, at
least.
next prev parent reply other threads:[~2023-08-18 5:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 22:12 [PATCH 0/3] Q40 IDE fixes Michael Schmitz
2023-08-17 22:12 ` [PATCH 1/3] m68k/q40: fix IO base selection for Q40 in pata_falcon.c Michael Schmitz
2023-08-18 0:42 ` Damien Le Moal
2023-08-18 2:53 ` Michael Schmitz
2023-08-18 5:33 ` Finn Thain [this message]
2023-08-19 20:29 ` Sergey Shtylyov
2023-08-20 19:19 ` Michael Schmitz
2023-08-21 7:46 ` Michael Schmitz
2023-08-17 22:12 ` [PATCH 2/3] m68k/q40: add data_swab option for pata_falcon to byte-swap disk data Michael Schmitz
2023-08-18 0:51 ` Damien Le Moal
2023-08-18 3:08 ` Michael Schmitz
2023-08-18 3:15 ` Damien Le Moal
2023-08-18 4:01 ` Michael Schmitz
2023-08-20 18:07 ` Sergey Shtylyov
2023-08-20 19:27 ` Michael Schmitz
2023-08-22 19:10 ` Sergei Shtylyov
2023-08-22 19:44 ` Sergei Shtylyov
2023-08-22 20:21 ` Michael Schmitz
2023-08-17 22:12 ` [PATCH 3/3] m68k/atari: change Falcon IDE platform device to id 0 Michael Schmitz
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=ef903aa8-25aa-779b-cf88-33840b498282@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=dlemoal@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=rz@linux-m68k.org \
--cc=s.shtylyov@omp.ru \
--cc=schmitzmic@gmail.com \
--cc=stable@vger.kernel.org \
--cc=will@sowerbutts.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