[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6580d606467d1_715492946@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date: Mon, 18 Dec 2023 15:30:14 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Ira Weiny <ira.weiny@...el.com>, Jonathan Cameron
<Jonathan.Cameron@...wei.com>
CC: Fan Ni <nifan.cxl@...il.com>, Dave Jiang <dave.jiang@...el.com>,
<linux-cxl@...r.kernel.org>, <linux-kernel@...r.kernel.org>, Huai-Cheng Kuo
<hchkuo@...ry-design.com.tw>
Subject: Re: [PATCH v2 2/2] cxl/cdat: Fix header sum value in CDAT checksum
Ira Weiny wrote:
> Jonathan Cameron wrote:
> > On Wed, 29 Nov 2023 17:33:04 -0800
> > Ira Weiny <ira.weiny@...el.com> wrote:
> >
>
> [snip]
>
> > > [1] https://lore.kernel.org/all/20231116-fix-cdat-devm-free-v1-1-b148b40707d7@intel.com/
> > >
> > > Fixes: aba578bdace5 ("hw/cxl/cdat: CXL CDAT Data Object Exchange implementation")
> > > Cc: Huai-Cheng Kuo <hchkuo@...ry-design.com.tw>
> > > Signed-off-by: Ira Weiny <ira.weiny@...el.com>
> >
> > This only becomes a problem with the addition of DCDs so I'm not going to rush it in.
>
> That makes sense.
>
> > Btw cc qemu-devel on qemu patches!
> >
>
> Ah... yea my bad.
Might I also ask for a more prominent way to quickly identify kernel vs
qemu patches, like a "[QEMU PATCH]" prefix? I tend to look for "hw/" in
the diff path names, but the kernel vs qemu question is ambiguous when
looking at the linux-cxl Patchwork queue.
@Jonathan, what do you think of having the kernel patchwork-bot watch
your tree for updating patch state (if it is not happening already).
Powered by blists - more mailing lists