[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66d8f41cb3e6_3975294f9@dwillia2-xfh.jf.intel.com.notmuch>
Date: Wed, 4 Sep 2024 16:58:20 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "Huang, Ying" <ying.huang@...el.com>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>
CC: Andrew Morton <akpm@...ux-foundation.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>, Dan Williams
<dan.j.williams@...el.com>, David Hildenbrand <david@...hat.com>, "Davidlohr
Bueso" <dave@...olabs.net>, Jonathan Cameron <jonathan.cameron@...wei.com>,
Dave Jiang <dave.jiang@...el.com>, Alison Schofield
<alison.schofield@...el.com>, Vishal Verma <vishal.l.verma@...el.com>, "Ira
Weiny" <ira.weiny@...el.com>, Alistair Popple <apopple@...dia.com>, "Bjorn
Helgaas" <bhelgaas@...gle.com>, Baoquan He <bhe@...hat.com>
Subject: Re: [PATCH -v2] Resource: fix region_intersects() for CXL memory
Huang, Ying wrote:
> Hi, Andy,
>
> Thanks for your comments!
>
> Andy Shevchenko <andriy.shevchenko@...ux.intel.com> writes:
[..]
>
> > You may move Cc list after '---', so it won't unnecessarily pollute the commit
> > message.
>
> Emm... It appears that it's a common practice to include "Cc" in the
> commit log.
Yes, just ignore this feedback, it goes against common practice. Cc list
as is looks sane to me.
Powered by blists - more mailing lists