public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	Christoph Hellwig <hch@lst.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block driver updates for 5.14-rc1
Date: Wed, 30 Jun 2021 14:10:12 -0600	[thread overview]
Message-ID: <bf8b1ca0-4362-dc86-3933-efd609fe3827@kernel.dk> (raw)
In-Reply-To: <CAHk-=wg6axLJQuFQBNa+nMHkEdx4X75LF7_P=eC=rzKj0x2h2A@mail.gmail.com>

On 6/30/21 1:29 PM, Linus Torvalds wrote:
> On Tue, Jun 29, 2021 at 12:55 PM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Note that this will throw a trivial merge conflict in
>> drivers/nvme/host/fabrics.c due to the NVME_SC_HOST_PATH_ERROR addition.
> 
> Grr.
> 
> I don't mind the conflict. It's trivial, as you say.
> 
> I *do* mind what the conflict unearthed: commit 63d20f54a3d0
> ("nvme-fabrics: remove extra new lines in the switch").
> 
> That commit claims to remove new-lines. In fact, the full commit
> message explicitly says "No functionality change in this patch".
> 
> Except what it does is not just non-functional whitespace cleanup. No,
> it adds that
> 
>         case NVME_SC_HOST_PATH_ERROR:
> 
> thing that was added in mainline too by commit 4d9442bf263a
> ("nvme-fabrics: decode host pathing error for connect").
> 
> THAT is not ok. Commit messages that explicitly say one thing, and
> then do something completely different are very bad.

Agree, that's beyond ugly, I should have caught that.

-- 
Jens Axboe


  reply	other threads:[~2021-06-30 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 19:55 [GIT PULL] Block driver updates for 5.14-rc1 Jens Axboe
2021-06-30 19:29 ` Linus Torvalds
2021-06-30 20:10   ` Jens Axboe [this message]
2021-06-30 20:13   ` Chaitanya Kulkarni
2021-06-30 20:21 ` pr-tracker-bot

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=bf8b1ca0-4362-dc86-3933-efd609fe3827@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=torvalds@linux-foundation.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