From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-block@vger.kernel.org, axboe@kernel.dk,
linux-m68k@vger.kernel.org, chzigotzky@xenosoft.de, hch@lst.de,
martin@lichtvoll.de, stable@vger.kernel.org
Subject: Re: [PATCH v4 1/1] block: bugfix for Amiga partition overflow check patch
Date: Thu, 6 Jul 2023 07:25:37 +1200 [thread overview]
Message-ID: <def97c03-533d-4ce0-4303-e8465233bd7c@gmail.com> (raw)
In-Reply-To: <CAMuHMdVGNB_aZnDHw_wfDTinDk+LKkP1Lx96Cgm0jM6J1WdACQ@mail.gmail.com>
Hi Geert,
On 5/07/23 21:08, Geert Uytterhoeven wrote:
>
>>>> Fixes: b6f3f28f60 ("block: add overflow checks for Amiga partition support")
>>>> Message-ID: 024ce4fa-cc6d-50a2-9aae-3701d0ebf668@xenosoft.de
>>> Please drop this line.
>> Because it's redundant, as I've also used Link:?
> (That, too ;-)
>
> Because the use of the Message-ID: tag in patches is not documented.
Now I wonder where I picked up that habit ...
> IIRC, it might also cause issues when applying, as the downloaded patch
> will appear to have two Message-IDs.
That's correct (if you refer to a patch in mbox format), but from the
context of the two Message-ID lines, it ought to be clear which one
matters.
> I'm not sure the sample git hook in Documentation/maintainer/configure-git.rst
> (and all variants the various maintainers are using) handles this correctly.
You're right, it won't check for context there.
In this particular instance, it won't use my Message-ID tag anyway
though (forgot the angle brackets).
I'll fix that in v5 later.
Cheers,
Michael
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2023-07-05 19:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230620201725.7020-1-schmitzmic@gmail.com>
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
[not found] ` <20230704233808.25166-1-schmitzmic@gmail.com>
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 [this message]
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
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=def97c03-533d-4ce0-4303-e8465233bd7c@gmail.com \
--to=schmitzmic@gmail.com \
--cc=axboe@kernel.dk \
--cc=chzigotzky@xenosoft.de \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=martin@lichtvoll.de \
--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;
as well as URLs for NNTP newsgroup(s).