From: Dan Williams <dan.j.williams@intel.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Matthew Wilcox <willy@infradead.org>,
<kernel-janitors@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <nvdimm@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
"Dan Williams" <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Jane Chu" <jane.chu@oracle.com>
Subject: Re: [v5 0/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON
Date: Tue, 27 Jun 2023 10:25:59 -0700 [thread overview]
Message-ID: <649b1ba7495a3_8e17829485@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <ba6d2b6b-87b8-29c9-93a9-0026ee7ae7ca@web.de>
Markus Elfring wrote:
> >> Would you insist on the usage of cover letters also for single patches?
> >
> > I would neither insist on it, nor prohibit it.
>
> It seems that you can tolerate an extra message here.
>
>
> > It simply does not make enough difference.
>
> Can it occasionally be a bit nicer to receive all relevant information within a single patch
> instead of a combination of two messages?
No, I am the maintainer of this code and everything I needed to judge
this patch was provided. This cover letter only included inter-version
details and anything relevant for the kernel history is included in the
patch itself.
For any code I maintain inter-version details below the --- line or in a
0/1 cover letter are perfectly acceptable.
Please, if the review feedback is arbitrary, as it is in this case,
strongly consider not offering it.
prev parent reply other threads:[~2023-06-27 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 18:13 [PATCH v5 0/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON Jane Chu
2023-06-15 18:13 ` [PATCH v5 1/1] " Jane Chu
2023-06-25 5:51 ` Dan Williams
[not found] ` <b57afc45-6bf8-3849-856f-2873e60fcf97@web.de>
2023-06-26 17:49 ` [PATCH v5 0/1] " Jane Chu
[not found] ` <be3db57c-29d0-cfc9-f0cc-1765b672c57e@web.de>
2023-06-27 15:22 ` [v5 " Matthew Wilcox
[not found] ` <b46b90b5-cc1d-9311-892b-a0f8abe155d6@web.de>
2023-06-27 16:24 ` Matthew Wilcox
[not found] ` <ba6d2b6b-87b8-29c9-93a9-0026ee7ae7ca@web.de>
2023-06-27 17:25 ` Dan Williams [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=649b1ba7495a3_8e17829485@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Markus.Elfring@web.de \
--cc=brauner@kernel.org \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jane.chu@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@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).