From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Hans Holmberg <hans.holmberg@wdc.com>,
stable@vger.kernel.org, Zizhi Wo <wozizhi@huawei.com>
Subject: Re: [PATCH 5/7] xfs: fix off-by-one error in fsmap's end_daddr usage
Date: Thu, 14 Nov 2024 16:56:39 +0100 [thread overview]
Message-ID: <20241114155639.GA522@lst.de> (raw)
In-Reply-To: <20241114155535.GM9462@frogsfrogsfrogs>
On Thu, Nov 14, 2024 at 07:55:35AM -0800, Darrick J. Wong wrote:
> Er... I'm not sure why you're sending this patch to Hans and stable but
> not linux-xfs? Also it's already on the list, though nobody's responded
> to it yet:
That's because git-send-email has completely stupid defaults. I picked
it up as a baseline for some of my fsmap, and it just added random
Ccs :(
prev parent reply other threads:[~2024-11-14 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241114153353.318020-1-hch@lst.de>
2024-11-14 15:33 ` [PATCH 5/7] xfs: fix off-by-one error in fsmap's end_daddr usage Christoph Hellwig
2024-11-14 15:55 ` Darrick J. Wong
2024-11-14 15:56 ` Christoph Hellwig [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=20241114155639.GA522@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=stable@vger.kernel.org \
--cc=wozizhi@huawei.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