From: Dave Jiang <dave.jiang@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-cxl@vger.kernel.org, linux-pci@vger.kernel.org,
dan.j.williams@intel.com, ira.weiny@intel.com,
vishal.l.verma@intel.com, alison.schofield@intel.com,
Jonathan.Cameron@huawei.com, dave@stgolabs.net
Subject: Re: [PATCH v6 0/2] cxl: Region bandwidth calculation for targets with shared upstream link
Date: Tue, 2 Jul 2024 13:03:12 -0700 [thread overview]
Message-ID: <176fa351-1922-4e62-a1bd-c620d97b955f@intel.com> (raw)
In-Reply-To: <20240702164718.GA24910@bhelgaas>
On 7/2/24 9:47 AM, Bjorn Helgaas wrote:
> On Mon, Jul 01, 2024 at 02:49:13PM -0700, Dave Jiang wrote:
>> v6:
>> - Update kdoc in comments. (Ira)
>> - Various rearranging and cleanup of variable declarations. (Jonathan)
>
> Housekeeping nit: it's helpful to include the diffstat in the cover
> letter so I can tell whether I need to look at this, e.g., does it
> affect the subsystem I worry about? Also nice to have URLs and the
> brief changelog for previous versions.
>
Thanks Bjorn. Will do. stgit email used to include the diff stat. Not sure why they dropped the diff stats addition when they went to rust from python.
prev parent reply other threads:[~2024-07-02 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 21:49 [PATCH v6 0/2] cxl: Region bandwidth calculation for targets with shared upstream link Dave Jiang
2024-07-01 21:49 ` [PATCH v6 1/2] cxl: Preserve the CDAT access_coordinate for an endpoint Dave Jiang
2024-07-01 21:49 ` [PATCH v6 2/2] cxl: Calculate region bandwidth of targets with shared upstream link Dave Jiang
2024-07-04 0:58 ` Dan Williams
2024-07-04 14:03 ` Jonathan Cameron
2024-07-02 16:47 ` [PATCH v6 0/2] cxl: Region bandwidth calculation for " Bjorn Helgaas
2024-07-02 20:03 ` Dave Jiang [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=176fa351-1922-4e62-a1bd-c620d97b955f@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=helgaas@kernel.org \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@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