[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <670581c5e7e_174cb329467@dwillia2-xfh.jf.intel.com.notmuch>
Date: Tue, 8 Oct 2024 12:02:29 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, "Huang, Ying"
<ying.huang@...el.com>
CC: Dan Williams <dan.j.williams@...el.com>, Andrew Morton
<akpm@...ux-foundation.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>, "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>, Philip Li <philip.li@...el.com>
Subject: Re: [PATCH -v2] Resource: fix region_intersects() for CXL memory
Andy Shevchenko wrote:
[..]
> We have all tags and MAINTAINERS database. How do you know if those who
> are in the Cc list are really interested in receiving this? What make me
> sure is to have Author of the culprit commit, relevant mailing list and
> maintainers, also reviewers and testers, if any. All this information is
> available without Cc list. But if you *really* want it, you should
> follow the Link tag (for the new commits, for the past ~2+ years) and
> harvest it there. And actually I use that Link to reply to the thread
> directly. So, again, the Cc list in the commit message is a historical
> burden that consumes a lot of time and energy and should be gone in the
> future.
Andy, this debate is consuming more time and energy than any amount of
trimming Cc: lines from commits could save.
Powered by blists - more mailing lists