All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: <ira.weiny@intel.com>, <alucerop@amd.com>,
	<a.manzanares@samsung.com>, <dongjoo.seo1@samsung.com>,
	<mst@redhat.com>, <marcel.apfelbaum@gmail.com>,
	<armbru@redhat.com>, <linux-cxl@vger.kernel.org>,
	<qemu-devel@nongnu.org>
Subject: Re: [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate
Date: Wed, 17 Dec 2025 13:59:30 +0000	[thread overview]
Message-ID: <20251217135930.00004616@huawei.com> (raw)
In-Reply-To: <20251216011211.anwnw25ot6n3euhq@offworld>

On Mon, 15 Dec 2025 17:12:11 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:

> ping? If there are no further issues, could this be picked up into
> your jic23 tree?
> 
> Thanks,
> Davidlohr
> 
Hi Davidlohr,

I'm just waiting on the 10.2 release before bringing my tree up to
date and reposting the various series that I consider ready which
didn't get merged in 10.2.

Then I'll figure out where in the tree to push these in.  I might
do the leg work for that before the release, but given that should
happen shortly I'll not push a tree out on gitlab until after that.

Jonathan

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: <ira.weiny@intel.com>, <alucerop@amd.com>,
	<a.manzanares@samsung.com>, <dongjoo.seo1@samsung.com>,
	<mst@redhat.com>, <marcel.apfelbaum@gmail.com>,
	<armbru@redhat.com>, <linux-cxl@vger.kernel.org>,
	<qemu-devel@nongnu.org>
Subject: Re: [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate
Date: Wed, 17 Dec 2025 13:59:30 +0000	[thread overview]
Message-ID: <20251217135930.00004616@huawei.com> (raw)
In-Reply-To: <20251216011211.anwnw25ot6n3euhq@offworld>

On Mon, 15 Dec 2025 17:12:11 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:

> ping? If there are no further issues, could this be picked up into
> your jic23 tree?
> 
> Thanks,
> Davidlohr
> 
Hi Davidlohr,

I'm just waiting on the 10.2 release before bringing my tree up to
date and reposting the various series that I consider ready which
didn't get merged in 10.2.

Then I'll figure out where in the tree to push these in.  I might
do the leg work for that before the release, but given that should
happen shortly I'll not push a tree out on gitlab until after that.

Jonathan


  reply	other threads:[~2025-12-17 13:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 19:52 [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 1/5] hw/pcie: Support enabling flit mode Davidlohr Bueso
2025-12-18 16:31   ` Jonathan Cameron
2025-12-18 16:31     ` Jonathan Cameron via
2025-11-03 19:52 ` [PATCH 2/5] hw/cxl: Refactor component register initialization Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 3/5] hw/cxl: Allow BI by default in Window restrictions Davidlohr Bueso
2025-12-18  9:18   ` Markus Armbruster
2025-12-18 15:48     ` Jonathan Cameron
2025-12-18 15:48       ` Jonathan Cameron via
2025-12-18 15:59       ` Markus Armbruster
2025-12-19 17:53         ` Jonathan Cameron
2025-12-19 17:53           ` Jonathan Cameron via
2025-11-03 19:52 ` [PATCH 4/5] hw/cxl: Support type3 HDM-DB Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 5/5] hw/cxl: Remove register special_ops->read() Davidlohr Bueso
2025-12-16  1:12 ` [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate Davidlohr Bueso
2025-12-17 13:59   ` Jonathan Cameron [this message]
2025-12-17 13:59     ` Jonathan Cameron via
2025-12-23 11:53     ` Jonathan Cameron
2025-12-23 11:53       ` Jonathan Cameron via
2025-12-30 18:23       ` Davidlohr Bueso
2026-01-02 16:35         ` Jonathan Cameron
2026-01-02 16:35           ` Jonathan Cameron via
2025-12-16  6:53 ` Markus Armbruster
2025-12-16 15:24   ` Davidlohr Bueso
2025-12-17  7:51     ` Markus Armbruster

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=20251217135930.00004616@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=alucerop@amd.com \
    --cc=armbru@redhat.com \
    --cc=dave@stgolabs.net \
    --cc=dongjoo.seo1@samsung.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.