linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pierre-Elliott Bécue" <peb@debian.org>
To: linux-rdma@vger.kernel.org
Subject: Re: What's the current status with bnxt_re-abi.h
Date: Wed, 12 Jun 2024 18:51:23 +0200	[thread overview]
Message-ID: <87frticdf8.fsf@daath.pimeys.fr> (raw)
In-Reply-To: <87jziucdlj.fsf@daath.pimeys.fr> ("Pierre-Elliott Bécue"'s message of "Wed, 12 Jun 2024 18:47:36 +0200")

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

Pierre-Elliott Bécue <peb@debian.org> wrote on 12/06/2024 at 18:47:36+0200:

> Hello,
>
> In bnxt_re-abi.h, the abi version mentioned is 1. It's used as it's in
> all libibverbs to determine the min AND max supported ABI.
>
> bnxt_re isn't currently mainlined in the kernel,

Sorry, a word is missing: "Recent bnxt_re isn't currently mainlined"

> and those eager to use
> the driver need to rely on the one provided by broadcom on their
> website.
>
> The thing is, they bumped their ABI version multiple times (current is
> 6). In the current context, one can't use the manually compiled bnxt_re
> driver with libibverbs as any call will error due to the bnxt_re abi
> version being outside of min/max supported abi version.
>
> What's the current situation regarding bnxt_re, should we consider
> libibverb support of bnxt_re as deprecated?
>
> Of course I could have missed something, sorry for that if that's the
> case.
>
> Bests,

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

  reply	other threads:[~2024-06-12 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 16:47 What's the current status with bnxt_re-abi.h Pierre-Elliott Bécue
2024-06-12 16:51 ` Pierre-Elliott Bécue [this message]
2024-06-12 17:16   ` Selvin Xavier
2024-06-12 18:29     ` Pierre-Elliott Bécue
2024-06-13  8:49       ` Selvin Xavier
2024-06-13  9:13         ` Pierre-Elliott Bécue

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=87frticdf8.fsf@daath.pimeys.fr \
    --to=peb@debian.org \
    --cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).