Message ID | 20220404021216.66841-1-dave@stgolabs.net |
---|---|
Headers | show |
Series | cxl/mbox: Robustify handling of mbox_cmd.return_code | expand |
On Sun, Apr 3, 2022 at 7:12 PM Davidlohr Bueso <dave@stgolabs.net> wrote: > > Hi, > > Changes from v1 (https://lore.kernel.org/all/20220317234049.69323-1-dave@stgolabs.net/): > - Patch 1 now just removes the lock comment, instead of moving it. (Dan) > - Modified pach 3 to use CPP hackery + misc table improvements. (Dan and Adam) > - Dropped patch 5 per concerns about implications with FW. (Dan) > - Picked up Adam's review tags. > > Currently the return_code from a completed mbox command is handled as > either successful or not. This series teaches the driver to better deal > with the different returns from the hardware, allowing better debugging > and mapping to proper kernel errno semantics (which are left unchanged > for now) as well as more ad-hoc handling. > > Applies against linux-cxl's next branch. > > Patches 1 and 2 are small nits. > Patch 3 and 4 implement and use the new calls. > > Thanks! Looks good to me, applied to cxl/pending for 5.19