Linux filesystem development
 help / color / mirror / Atom feed
From: Pankaj Raghav <pankaj.raghav@linux.dev>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
	da.gomez@kernel.org, gost.dev@samsung.com
Subject: Re: [PATCH] iomap: only follow dio alignment requirement if specified
Date: Tue, 27 Oct 2026 12:14:48 +0100	[thread overview]
Message-ID: <3048fa10-007e-41d1-9b95-5be5923e4a68@linux.dev> (raw)
In-Reply-To: <04a7e656-567d-458c-99b0-e9aa5960bd99@gmx.com>



On 10/27/2026 11:12 AM, Qu Wenruo wrote:
> 
> 
> 在 2026/10/27 20:37, Pankaj Raghav 写道:
>>
>>
> [...]
>>>>> Cc: stable@vger.kernel.org
>>
>> FYI, your patches are not in 7.3 and only in linux-next. So we don't need to 
>> cc stable?
> 
> Unfortunately, it's already upstreamed.
> 
> The commit hash, 4025185cf953 ("iomap: follow the alignment requirement for 
> iomap_dio_hole_iter()"), is already in the upstream.
> 
Yes. My point is this was merged as a part of the current v7.4 merge window, so 
the fixes can go as a part of RCs? Does it still require a CC to stable?

--
Pankaj

      reply	other threads:[~2026-10-27 11:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  6:48 [PATCH] iomap: only follow dio alignment requirement if specified Qu Wenruo
2026-10-26 14:21 ` Pankaj Raghav (Samsung)
2026-10-26 19:49 ` Pankaj Raghav (Samsung)
2026-10-26 20:59   ` Qu Wenruo
2026-10-26 21:29     ` Qu Wenruo
2026-10-27 10:07     ` Pankaj Raghav
2026-10-27 10:12       ` Qu Wenruo
2026-10-27 11:14         ` Pankaj Raghav [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=3048fa10-007e-41d1-9b95-5be5923e4a68@linux.dev \
    --to=pankaj.raghav@linux.dev \
    --cc=da.gomez@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=stable@vger.kernel.org \
    --cc=wqu@suse.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