From: Dan Williams <dan.j.williams@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
Linux MM <linux-mm@kvack.org>,
Linux NVDIMM <nvdimm@lists.linux.dev>
Subject: Re: [PATCH] mm: don't include <linux/dax.h> in <linux/mempolicy.h>
Date: Tue, 21 Sep 2021 11:26:11 -0700 [thread overview]
Message-ID: <CAPcyv4j4VbQMBZou_=9JD5pZbBoFo_ccL=OLXofLPHHJY6JDAw@mail.gmail.com> (raw)
In-Reply-To: <20210921082253.1859794-1-hch@lst.de>
On Tue, Sep 21, 2021 at 1:23 AM Christoph Hellwig <hch@lst.de> wrote:
>
> Not required at all, and having this causes a huge kernel rebuild
> as soon as something in dax.h changes.
Looks good.
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
prev parent reply other threads:[~2021-09-21 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 8:22 [PATCH] mm: don't include <linux/dax.h> in <linux/mempolicy.h> Christoph Hellwig
2021-09-21 8:47 ` Naoya Horiguchi
2021-09-21 18:26 ` 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='CAPcyv4j4VbQMBZou_=9JD5pZbBoFo_ccL=OLXofLPHHJY6JDAw@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=nvdimm@lists.linux.dev \
/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).