From: Dan Williams <dan.j.williams@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, <dan.j.williams@intel.com>
Cc: <dave.jiang@intel.com>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<Jonathan.Cameron@huawei.com>, <fan.ni@samsung.com>,
<a.manzanares@samsung.com>, <dave@stgolabs.net>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 0/4] cxl: Handle background commands
Date: Tue, 23 May 2023 14:03:53 -0700 [thread overview]
Message-ID: <646d2a394342c_33fb3294bf@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230523170927.20685-1-dave@stgolabs.net>
Davidlohr Bueso wrote:
> Hi,
>
> This is the latest iteration of the synchronous background command handling
> work. Currently there are no users, but it is expected that firmware update
> and scan media be the first two to use it.
>
> Patches 1-3 are requirements for the actual patch 4.
>
> Changes from v1/v2 (https://lore.kernel.org/linux-cxl/20230502171841.21317-1-dave@stgolabs.net):
> o Picked up tags for patches 1 and 2.
> o Added more context to the changelog in the rcuwait patch 1. (Dan)
> o Added new patch 3 for common request irq functionality. (Dan)
> o Misc cleanups in patch 4. (Jonathan)
> o Don't clobber the ctrl settings. (Dan)
> o Removed bogus warning in irq handler. (Jonathan, Dan)
> o Make sleep uninterruptible and clarify in the changelog that
> timeouts are in fact unexpected.
>
> Applies against 'fixes' from cxl.git.
Like Linus I want to see the conflicts. Whenever possible base on latest
Linus tag like v6.4-rc3. In this case I will add this to a
for-6.5/cxl-background topic branch based on 'fixes' for now, but once
'fixes' hits v6.4-rc4 I will move the topic baseline just to have it not
be based on a random point in the history.
This also encourages me to be more proactive about getting fixes
upstream so that the next Linus tag can be used for development.
next prev parent reply other threads:[~2023-05-23 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 17:09 Davidlohr Bueso
2023-05-23 17:09 ` [PATCH 1/4] rcuwait: Support timeouts Davidlohr Bueso
2023-05-23 17:09 ` [PATCH 2/4] cxl/pci: Allocate irq vectors earlier during probe Davidlohr Bueso
2023-05-23 17:09 ` [PATCH 3/4] cxl/pci: Introduce cxl_request_irq() Davidlohr Bueso
2023-05-23 18:43 ` Dan Williams
2023-05-23 17:09 ` [PATCH 4/4] cxl/mbox: Add background cmd handling machinery Davidlohr Bueso
2023-05-23 21:03 ` Dan Williams [this message]
2023-05-23 21:59 ` [PATCH v3 0/4] cxl: Handle background commands Davidlohr Bueso
2023-05-24 4:19 ` Dan Williams
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=646d2a394342c_33fb3294bf@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.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=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®