linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Jane Chu <jane.chu@oracle.com>,
	nvdimm@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	kernel-janitors@vger.kernel.org,
	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>
Subject: Re: [v5 0/1] dax: enable dax fault handler to report VM_FAULT_HWPOISON
Date: Tue, 27 Jun 2023 16:22:06 +0100	[thread overview]
Message-ID: <ZJr+ngIH877t9seI@casper.infradead.org> (raw)
In-Reply-To: <be3db57c-29d0-cfc9-f0cc-1765b672c57e@web.de>

On Tue, Jun 27, 2023 at 08:08:19AM +0200, Markus Elfring wrote:
> > The thought was to put descriptions unsuitable for commit header in the cover letter.
> 
> How do you think about to put additional information below triple dashes
> (or even into improved change descriptions)?
> 
> See also:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.4#n686

Markus,

Please go away.  Your feedback is not helpful.  Thank you.

  parent reply	other threads:[~2023-06-27 15:22 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       ` Matthew Wilcox [this message]
     [not found]         ` <b46b90b5-cc1d-9311-892b-a0f8abe155d6@web.de>
2023-06-27 16:24           ` [v5 " Matthew Wilcox
     [not found]             ` <ba6d2b6b-87b8-29c9-93a9-0026ee7ae7ca@web.de>
2023-06-27 17:25               ` Dan Williams

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=ZJr+ngIH877t9seI@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Markus.Elfring@web.de \
    --cc=brauner@kernel.org \
    --cc=dan.j.williams@intel.com \
    --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 \
    /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).