From: Ben Widawsky <ben.widawsky@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Weiny, Ira" <ira.weiny@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH] cxl/cxlmem: Remove unused cxlmd field
Date: Wed, 3 Nov 2021 15:34:13 -0700 [thread overview]
Message-ID: <20211103223413.n6fmf3gtop56wssz@intel.com> (raw)
In-Reply-To: <CAPcyv4gQeZ6PUQswGe61Vd7u0qXOEL8V9Bp0FMJxfj480yh=LA@mail.gmail.com>
On 21-11-03 15:13:21, Dan Williams wrote:
> On Wed, Nov 3, 2021 at 1:41 PM <ira.weiny@intel.com> wrote:
> >
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > This field was left over when the connection between the cxl_memdev and
> > cxl_mem was tighter. It is no longer set nor used so remove it.[1]
> >
> > [1] https://lore.kernel.org/linux-cxl/CAPcyv4hcgh2gb8qsS_UXTBSGqYfMPnC6p5kkvNUjm+V6kVKM5g@mail.gmail.com/
>
> Looks good, although I'll probably fixup the subject to:
>
> cxl/memdev: Remove unused cxlmd field
>
> ...to start to standardize on a prefix format of
> cxl/$(infrastructure_area/C file name). Previous commits used
> "cxl/mem:", but I think going forward that prefix can be used for
> changes related to the driver in "cxl_mem.ko". Where "cxl/memdev:" is
> for changes related to the base 'struct cxl_memdev' infrastructure.
>
> The only reason that drivers/cxl/cxlmem.h has that redundant mention
> of "cxl" in filename is to avoid collisions with
> "arch/um/include/shared/mem.h" on ARCH=um builds. So "cxl/cxlmem:"
> triggered my naming finickiness.
I agree with the subject fixup, and patch is:
Acked-by: Ben Widawsky <ben.widawsky@intel.com>
I think there can be cases made for when it might not be a specific C file that
is in the subject, but this isn't one of them.
next prev parent reply other threads:[~2021-11-03 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 20:28 [INTERNAL PATCH 0/2] CXL: Clarify struct cxl_mem ira.weiny
2021-11-02 20:29 ` [INTERNAL PATCH 1/2] cxl/mbox: Remove bad comment ira.weiny
2021-11-02 20:29 ` [INTERNAL PATCH 2/2] cxl/cxlmem: Change cxl_mem to a more descriptive name ira.weiny
2021-11-03 1:53 ` Dan Williams
2021-11-03 13:51 ` Jonathan Cameron
2021-11-03 16:38 ` Dan Williams
2021-11-03 20:41 ` [PATCH] cxl/cxlmem: Remove unused cxlmd field ira.weiny
2021-11-03 22:13 ` Dan Williams
2021-11-03 22:34 ` Ben Widawsky [this message]
2021-11-10 17:40 ` [INTERNAL PATCH 2/2] cxl/cxlmem: Change cxl_mem to a more descriptive name Jonathan Cameron
2021-11-10 19:01 ` Ira Weiny
2021-11-02 20:34 ` [INTERNAL PATCH 0/2] CXL: Clarify struct cxl_mem 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=20211103223413.n6fmf3gtop56wssz@intel.com \
--to=ben.widawsky@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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