Re: [PATCH 00/11] Subject: [PATCH for-next 00/11] RDMA/cxi: add the HPE Cassini verbs driver

[Doug Ledford <doug.ledford@hpe.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2486 bytes --]

On 11/4/26 1:54 AM, Leon Romanovsky wrote:
> On Tue, Nov 03, 2026 at 10:30:04AM -0400, Jason Gunthorpe wrote:
>> On Tue, Nov 03, 2026 at 04:28:26PM +0200, Leon Romanovsky wrote:
>>> On Fri, Oct 30, 2026 at 09:35:28PM -0700, Doug Ledford wrote:
>>>> This series adds cxiverbs, an RDMA driver for the HPE Slingshot Cassini
>>>> NIC. It exposes the NIC through the verbs API using the UET reliable
>>>> unconnected (RU) queue pair type from the UET RDMA core series.
>>>>
>>>> cxiverbs does not drive the hardware itself. It is an auxiliary bus
>>>> client of the cxi-ss1 Cassini core driver and does everything through
>>>> that driver's exported CXI interface.
>>>
>>> <...>
>>>
>>>> Before posting, the series was reviewed with the Sashiko AI code
>>>> review tool and checkpatch. All valid findings are fixed, except the
>>>> open items listed above.
>>>
>>> <...>
>>>
>>>> ---
>>>> base-commit: 306a2f8432f516069b2e673de7a07043132c034f
>>>
>>> Sashiko failed to apply this series as this base-commit doesn't exist.
>>> ➜  kernel git:(wip/leon-for-rc) git show 306a2f8432f516069b2e673de7a07043132c034f
>>> fatal: bad object 306a2f8432f516069b2e673de7a07043132c034f
>>>
>>> https://sashiko.dev/#/patchset/20261030-cxi-for-next-v1-0-bc6e49e07037@hpe.com
>>>
>>> Please make sure that upstream sashiko runs on it too.
>>
>> I don't think he can, it relies on the core code series. I Don't know
>> how to instruct sashiko how to find another series to stich it
>> together
> 
> This may be a radical, unheard-of suggestion, but how about merging another
> series before sending follow-ups?

Well, we're caught in the "no dead code" rule trap.  Can't merge the UET
code because it has no consumer, and can't merge ours without it as a
consumer, so I have to make my branch based on their branch, and their
merge base went away.  They'll have to rebase and then I'll have to
rebase on theirs again.  But I expected a v3 for their code anyway, so
just whenever Eric gets around to fixing the Sashiko findings and
posting v3, I can rebase on that, and then the sashiko prompts can be
run.  But, FWIW, since the rdma portion of our submission was all brand
new code, it passed checkpatch and sashiko on our end.  It's the
existing code in the netdev tree that's where all the fun will be :-/.

-- 
Doug Ledford <doug.ledford@hpe.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]