From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Hellwig <hch@infradead.org>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
"Pankaj Raghav(Samsung)" <pankaj.raghav@linux.dev>
Subject: Re: [PATCH v3] iomap: only follow dio alignment requirement if specified
Date: Thu, 29 Oct 2026 05:01:31 -0700 [thread overview]
Message-ID: <auM1m0fflCf_JNw9@infradead.org> (raw)
In-Reply-To: <69074a82-05d3-4a51-b266-b74a23b39eb7@gmx.com>
On Thu, Oct 29, 2026 at 07:04:57AM +1030, Qu Wenruo wrote:
>
>
> 在 2026/10/29 01:56, Christoph Hellwig 写道:
> > Can you please write a normal commit log for this? I.e. explain the
> > problem and the highlevel fix in short sentences. No need for [] tags
> > or xfstests output.
>
> I think this is really up to personal tastes.
To a minor point, yes. But there's also plenty of fully objective
reasons against this style. One is that is inconsistent with the rest of
the iomap commit message. Please stick to the style of the surrounding
code, and that includes the commit message style.
The second is that this style is not good for bisecting or understanding
the code. It takes 2 and half pages of scrolling before getting to any
useful information. There is way to much information in here that
does not help understanding the change.
> I understand that too detailed commit message is slowing down the review,
> but if someone else in the future needs to re-check this commit, I guess
> they would prefer more details than less.
Quite to the contrary.
prev parent reply other threads:[~2026-10-29 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 23:28 [PATCH v3] iomap: only follow dio alignment requirement if specified Qu Wenruo
2026-10-28 15:26 ` Christoph Hellwig
2026-10-28 20:34 ` Qu Wenruo
2026-10-29 12:01 ` 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=auM1m0fflCf_JNw9@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pankaj.raghav@linux.dev \
--cc=quwenruo.btrfs@gmx.com \
--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