From: Christoph Hellwig <hch@infradead.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v1 1/2] nvme: drop multipath config option
Date: Wed, 26 Jul 2023 06:11:48 -0700 [thread overview]
Message-ID: <ZMEblNUKKKz+XvPX@infradead.org> (raw)
In-Reply-To: <7risd4kfoey3mkwsjr2hd5ofxawvjenjv6h4x76p6gepzoygll@cwap52i6hwg2>
On Tue, Jul 25, 2023 at 08:05:25AM +0200, Daniel Wagner wrote:
> On Mon, Jul 24, 2023 at 09:51:32AM -0700, Christoph Hellwig wrote:
> > Btw, Daniel - any reason you didn't Cc me on this?
>
> I thought you preferred not to be Cc. I am just trying to be nice :)
Heh. I usually try to avoid being Cced by the crazy get_maintainer
heuristics, because that means I get Cced on everything. For
things I maintain the Cc really helps getting my attention when
I'm overscheduled like now and might be way behind on the lists.
next prev parent reply other threads:[~2023-07-26 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 8:41 [PATCH v1 0/2] Remove CONFIG_NVME_MULTIPATH option Daniel Wagner
2023-07-19 8:41 ` [PATCH v1 1/2] nvme: drop multipath config option Daniel Wagner
2023-07-19 10:04 ` Keith Busch
2023-07-19 11:13 ` Daniel Wagner
2023-07-19 11:38 ` Keith Busch
2023-07-19 12:12 ` Daniel Wagner
2023-07-19 13:19 ` Hannes Reinecke
2023-07-24 16:51 ` Christoph Hellwig
2023-07-24 16:51 ` Christoph Hellwig
2023-07-25 6:05 ` Daniel Wagner
2023-07-26 13:11 ` Christoph Hellwig [this message]
2023-07-19 8:41 ` [PATCH v1 2/2] nvme: remove warning for shared ns when multipath=N Daniel Wagner
2023-07-24 16:53 ` Christoph Hellwig
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=ZMEblNUKKKz+XvPX@infradead.org \
--to=hch@infradead.org \
--cc=dwagner@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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).