linux-kernel - RE: [PATCH v3 0/4] cxl: Handle background commands

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <646d2a394342c_33fb3294bf@dwillia2-xfh.jf.intel.com.notmuch>
Date:   Tue, 23 May 2023 14:03:53 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     Davidlohr Bueso <dave@...olabs.net>, <dan.j.williams@...el.com>
CC:     <dave.jiang@...el.com>, <alison.schofield@...el.com>,
        <vishal.l.verma@...el.com>, <ira.weiny@...el.com>,
        <Jonathan.Cameron@...wei.com>, <fan.ni@...sung.com>,
        <a.manzanares@...sung.com>, <dave@...olabs.net>,
        <linux-cxl@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 0/4] cxl: Handle background commands

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.