From: Ira Weiny <ira.weiny@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jianpeng Ma <jianpeng.ma@intel.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] libnvdimm/pmem: remove unused header.
Date: Mon, 4 Jan 2021 14:18:58 -0800 [thread overview]
Message-ID: <20210104221858.GJ3097896@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <CAPcyv4gm-CnOAYqNYL29TUCQF04f9uCQOgF1ndRpu=_7e6T_kQ@mail.gmail.com>
On Mon, Jan 04, 2021 at 01:16:32PM -0800, Dan Williams wrote:
> On Mon, Dec 28, 2020 at 9:18 AM Ira Weiny <ira.weiny@intel.com> wrote:
> >
> > On Fri, Dec 25, 2020 at 09:35:46AM +0800, Jianpeng Ma wrote:
> > > 'commit a8b456d01cd6 ("bdi: remove BDI_CAP_SYNCHRONOUS_IO")' forgot
> >
> > This information should be part of a fixes tag.
>
> Oh, I was just about to comment "don't provide a Fixes tag for pure
> cleanups". Fixes is for functional issues that a backporter should
> consider.
I thought this was discussed recently and it was concluded that 'fixes' does
not indicate something should be backported?
...
https://lore.kernel.org/lkml/X8flmVAwl0158872@kroah.com/
At least that is what Greg KH said. But Dave C. was not happy with this...
:-/
Sorry...
Ira
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2021-01-04 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 1:35 [PATCH] libnvdimm/pmem: remove unused header Jianpeng Ma
2020-12-28 17:17 ` Ira Weiny
2021-01-04 21:16 ` Dan Williams
2021-01-04 22:18 ` Ira Weiny [this message]
2021-01-04 22:32 ` Dan Williams
2021-01-05 2:13 ` Ira Weiny
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=20210104221858.GJ3097896@iweiny-DESK2.sc.intel.com \
--to=ira.weiny@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jianpeng.ma@intel.com \
--cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.