From: Dan Williams <dan.j.williams@intel.com>
To: Dave Jiang <dave.jiang@intel.com>,
Adam Manzanares <a.manzanares@samsung.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"Fan Ni" <fan.ni@samsung.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"alison.schofield@intel.com" <alison.schofield@intel.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
"gourry.memverge@gmail.com" <gourry.memverge@gmail.com>,
"wj28.lee@gmail.com" <wj28.lee@gmail.com>,
"rientjes@google.com" <rientjes@google.com>,
"ruansy.fnst@fujitsu.com" <ruansy.fnst@fujitsu.com>,
"shradha.t@samsung.com" <shradha.t@samsung.com>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
Jim Harris <jim.harris@samsung.com>,
"mhocko@suse.com" <mhocko@suse.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] CXL Development Discussions
Date: Mon, 6 May 2024 15:58:25 -0700 [thread overview]
Message-ID: <663960911a914_2f63a294c0@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <3d18ae36-4dea-496a-a8fc-253b21135838@intel.com>
Dave Jiang wrote:
>
>
> On 5/6/24 12:27 PM, Adam Manzanares wrote:
> > Hello all,
> >
> > I would like to have a discussion with the CXL development community about
> > current outstanding issues and also invite developers interested in RAS and
> > memory tiering to participate.
> >
> > The first topic I believe we should discuss is how we can ensure as a group
> > that we are prioritizing upstream work. On a recent upstream CXL development
> > discussion call there was a call to review more work. I apologize for not
> > grabbing the link, but I believe Dave Jiang is leveraging patchwork and this
> > link should be shared with others so we can help get more reviews where needed.
>
> Bundle for the potential fixes
> https://patchwork.kernel.org/bundle/cxllinux/cxl-fixes/
>
> Bundle for the next merge window
> https://patchwork.kernel.org/bundle/cxllinux/cxl-next/
>
> Just be aware patchwork only takes patches, so the bundle are
> registered with the first patch of a series. The listing does display
> the origin series.
This seems solvable with a bit of scripting.
I went ahead and fixed up one of the series (CXL 1.1 link stattus) to
include all the patches in the bundle. I think it is useful to have a
one-stop shop for the queue and the state of review / testing.
Let me know if that makes things easier.
next prev parent reply other threads:[~2024-05-06 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240506192712uscas1p225316f79bb69f979b647d2a06a00a25f@uscas1p2.samsung.com>
2024-05-06 19:27 ` [LSF/MM/BPF TOPIC] CXL Development Discussions Adam Manzanares
2024-05-06 20:28 ` Dave Jiang
2024-05-06 22:58 ` Dan Williams [this message]
2024-05-08 18:08 ` Adam Manzanares
2024-05-06 23:47 ` Dan Williams
2024-05-07 18:50 ` Luis Chamberlain
2024-05-08 18:38 ` Adam Manzanares
2024-05-08 19:30 ` Luis Chamberlain
2024-05-09 18:14 ` Song Liu
2024-05-09 4:19 ` Dan Williams
2024-05-08 18:26 ` Adam Manzanares
2024-05-07 11:48 ` Michal Hocko
2024-05-08 18:35 ` Adam Manzanares
2024-05-12 13:07 ` Michal Hocko
2024-05-13 12:12 ` Davidlohr Bueso
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=663960911a914_2f63a294c0@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=gourry.memverge@gmail.com \
--cc=ira.weiny@intel.com \
--cc=jim.harris@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=ruansy.fnst@fujitsu.com \
--cc=shradha.t@samsung.com \
--cc=vishal.l.verma@intel.com \
--cc=wj28.lee@gmail.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;
as well as URLs for NNTP newsgroup(s).