All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-cxl@vger.kernel.org, David Hildenbrand <david@redhat.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <ira.weiny@intel.com>,
	Alistair Popple <apopple@nvidia.com>,
	Bjorn Helgaas <bhelgaas@google.com>, Baoquan He <bhe@redhat.com>,
	Philip Li <philip.li@intel.com>
Subject: Re: [PATCH -v2] Resource: fix region_intersects() for CXL memory
Date: Tue, 8 Oct 2024 22:18:18 +0300	[thread overview]
Message-ID: <ZwWFeo1zV4JGpTLw@black.fi.intel.com> (raw)
In-Reply-To: <670581c5e7e_174cb329467@dwillia2-xfh.jf.intel.com.notmuch>

On Tue, Oct 08, 2024 at 12:02:29PM -0700, Dan Williams wrote:
> 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.

Okay, okay, I'm giving up...
...with a thought that this planet is doomed.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-10-08 19:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  2:34 [PATCH -v2] Resource: fix region_intersects() for CXL memory Huang Ying
2024-08-19  8:13 ` Andy Shevchenko
2024-09-04  7:48   ` Huang, Ying
2024-09-04 12:43     ` Andy Shevchenko
2024-09-05  3:00       ` Huang, Ying
2024-09-05 10:57         ` Andy Shevchenko
2024-09-04 23:58     ` Dan Williams
2024-09-05 10:56       ` Andy Shevchenko
2024-09-05 11:08         ` David Hildenbrand
2024-09-05 12:36           ` Andy Shevchenko
2024-09-05 12:42             ` David Hildenbrand
2024-09-05 12:50               ` Andy Shevchenko
2024-09-05 12:57                 ` David Hildenbrand
2024-10-07 14:24                   ` Andy Shevchenko
2024-09-05 21:37         ` Dan Williams
2024-10-07 14:16           ` Andy Shevchenko
2024-09-06  1:07         ` Huang, Ying
2024-10-07 14:12           ` Andy Shevchenko
2024-10-08  2:52             ` Huang, Ying
2024-10-08 17:01               ` Andy Shevchenko
2024-10-08 19:02                 ` Dan Williams
2024-10-08 19:18                   ` Andy Shevchenko [this message]
2024-08-21 18:46 ` Bjorn Helgaas
2024-08-22  1:43   ` Dan Williams
2024-08-22 21:29     ` Bjorn Helgaas
2024-09-04 23:58       ` Dan Williams
2024-08-30  6:43     ` Huang, Ying

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=ZwWFeo1zV4JGpTLw@black.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alison.schofield@intel.com \
    --cc=apopple@nvidia.com \
    --cc=bhe@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=david@redhat.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=philip.li@intel.com \
    --cc=vishal.l.verma@intel.com \
    --cc=ying.huang@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 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.