public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Michael Schmitz <schmitzmic@gmail.com>, linux-block@vger.kernel.org
Cc: linux-m68k@vger.kernel.org, chzigotzky@xenosoft.de,
	geert@linux-m68k.org, hch@lst.de, martin@lichtvoll.de,
	stable@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v4 1/1] block: bugfix for Amiga partition overflow check patch
Date: Wed, 5 Jul 2023 16:38:36 -0600	[thread overview]
Message-ID: <c9bcd3ca-8260-3f29-26d1-0c00e2b098a3@kernel.dk> (raw)
In-Reply-To: <481c0e2a-320c-e53d-2a0e-ba5fa6ea4049@kernel.dk>

On 7/5/23 4:34?PM, Jens Axboe wrote:
> On 7/5/23 4:25?PM, Michael Schmitz wrote:
>> Hi Jens,
>>
>> On 6/07/23 10:13, Jens Axboe wrote:
>>>>> should be enough for it to go into stable from 5.2 and onwards.
>>>> OK - I wasn't certain whether you wanted the Fixes or stable tag dropped.
>>>>>> (Greg didn't seem to object to the Fixes: as such, just to the
>>>>>> incorrect version prereq)
>>>>> I think it's really confusing... A patch should only have a Fixes tag if
>>>>> it's fixing a specific bug in that patch. Either it is, in which case
>>>>> you would not need Cc stable at all since it's only in 6.5-rc, or it
>>>> It is fixing a bug in b6f3f28f60. I should have checked whether the
>>>> patch series had already gone to release, not just -rc, instead of
>>>> just adding the stable tag out of caution.
>>> But this is the confusion - if it's fixing a bug in b6f3f28f60, then why
>>> is it marked as needing to get backported much further back, predating
>>> that commit?
>>
>> I see - it doesn't need to be backported that far back _alone_. It
>> only needs to be applied after  b6f3f28f60 once that one has been
>> backported.
> 
> OK I see - I think there's some serious misunderstandings here then :-)
> 
> It sounds like it fixes a bug in b6f3f28f60 alone, and it has no
> business going into stable. The commit should _just_ be marked with it
> fixing that. If someone were to backport that previous series, then
> their tooling or diligence should notice this dependency and this
> current commit should be picked as well.
> 
> There should be no Cc: stable on this patch at all, I'll fix it up.

Here's what I have:

https://git.kernel.dk/cgit/linux/commit/?h=block-6.5&id=7eb1e47696aa231b1a567846bbe3a1e1befe1854

which has the following manual edits:

1) Change the title/subject line of the patch. "bugfix for Amiga
partition overflow check patch" means very little. The fact that this
patch is a bug fix for a previous commit is explicit with the Fixes
line.

2) Break lines at 72-74 chars, yours were very short.

3) Drop message-id

4) Drop cc stable tag

5) Drop the revision history. This should be behind three '---' lines
and then it's dropped automatically.

Let's hope this is it for Amiga partition handling!

-- 
Jens Axboe


  reply	other threads:[~2023-07-05 22:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 20:17 [PATCH v13 0/3] Amiga RDB partition support fixes Michael Schmitz
2023-06-20 20:17 ` [PATCH v13 1/3] block: fix signed int overflow in Amiga partition support Michael Schmitz
2023-06-20 20:17 ` [PATCH v13 2/3] block: change all __u32 annotations to __be32 in affs_hardblocks.h Michael Schmitz
2023-06-20 20:17 ` [PATCH v13 3/3] block: add overflow checks for Amiga partition support Michael Schmitz
2023-06-20 20:28 ` [PATCH v13 0/3] Amiga RDB partition support fixes Jens Axboe
2023-06-20 21:16   ` Martin Steigerwald
2023-06-21  5:54     ` John Paul Adrian Glaubitz
2023-06-20 21:17   ` Michael Schmitz
2023-07-04 23:38 ` [PATCH v4 0/1] Bugfix for Amiga partition fixes Michael Schmitz
2023-07-04 23:38   ` [PATCH v4 1/1] block: bugfix for Amiga partition overflow check patch Michael Schmitz
2023-07-05  7:28     ` Geert Uytterhoeven
2023-07-05  8:53       ` Michael Schmitz
2023-07-05  9:08         ` Geert Uytterhoeven
2023-07-05 19:25           ` Michael Schmitz
2023-07-05 20:42     ` Jens Axboe
2023-07-05 21:41       ` Michael Schmitz
2023-07-05 21:44         ` Jens Axboe
2023-07-05 22:09           ` Michael Schmitz
2023-07-05 22:13             ` Jens Axboe
2023-07-05 22:25               ` Michael Schmitz
2023-07-05 22:34                 ` Jens Axboe
2023-07-05 22:38                   ` Jens Axboe [this message]
2023-07-05 23:54                     ` Michael Schmitz
2023-07-06  7:23                       ` Martin Steigerwald

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=c9bcd3ca-8260-3f29-26d1-0c00e2b098a3@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chzigotzky@xenosoft.de \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    --cc=schmitzmic@gmail.com \
    --cc=stable@vger.kernel.org \
    /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