From: Peter Delevoryas <peter@pjd.dev>
To: Paolo Abeni <pabeni@redhat.com>
Cc: sam@mendozajonas.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, joel@jms.id.au, gwshan@linux.vnet.ibm.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] net/ncsi: Add NC-SI 1.2 Get MC MAC Address command
Date: Thu, 22 Dec 2022 09:13:57 -0800 [thread overview]
Message-ID: <9D98FD36-FA3B-4C9C-A470-69A52FD80677@pjd.dev> (raw)
In-Reply-To: <8a0a90511222d3161bfe2984f6b14f82206b8930.camel@redhat.com>
> On Dec 22, 2022, at 2:44 AM, Paolo Abeni <pabeni@redhat.com> wrote:
>
> On Tue, 2022-12-20 at 21:22 -0800, Peter Delevoryas wrote:
>> NC-SI 1.2 isn't officially released yet, but the DMTF takes way too long
>> to finalize stuff, and there's hardware out there that actually supports
>> this command (Just the Broadcom 200G NIC afaik).
>>
>> The work in progress spec document is here:
>>
>> https://www.dmtf.org/sites/default/files/standards/documents/DSP0222_1.2WIP90_0.pdf
>>
>> The command code is 0x58, the command has no data, and the response
>> returns a variable-length array of MAC addresses for the BMC.
>>
>> I've tested this out using QEMU emulation (I added the Mellanox OEM Get
>> MAC Address command to libslirp a while ago [1], although the QEMU code
>> to use it is still not in upstream QEMU [2] [3]. I worked on some more
>> emulation code for this as well), and on the new Broadcom 200G NIC.
>>
>> The Nvidia ConnectX-7 NIC doesn't support NC-SI 1.2 yet afaik. Neither
>> do older versions in newer firmware, they all just report NC-SI 1.1.
>>
>> Let me know what I can do to change this patch to be more suitable for
>> upstreaming, I'm happy to work on it more!
>
> This series is targeting the net-next tree, you should include such tag
> into the patch subjected.
>
> We have already submitted the networking pull request to Linus
> for v6.2 and therefore net-next is closed for new drivers, features,
> code refactoring and optimizations. We are currently accepting
> bug fixes only.
> Please repost when net-next reopens after Jan 2nd.
I see, thanks, I’ll resubmit later.
>
> RFC patches sent for review only are obviously welcome at any time.
Oh good point, I should have submitted it as an RFC.
>
> Thanks,
>
> Paolo
>
prev parent reply other threads:[~2022-12-22 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 5:22 Peter Delevoryas
2022-12-21 5:22 ` [PATCH 1/3] net/ncsi: Simplify Kconfig/dts control flow Peter Delevoryas
2022-12-21 5:22 ` [PATCH 2/3] net/ncsi: Fix netlink major/minor version numbers Peter Delevoryas
2022-12-21 5:22 ` [PATCH 3/3] net/ncsi: Add NC-SI 1.2 Get MC MAC Address command Peter Delevoryas
2022-12-22 10:53 ` Paolo Abeni
2022-12-22 17:18 ` Peter Delevoryas
2022-12-22 10:44 ` [PATCH 0/3] " Paolo Abeni
2022-12-22 17:13 ` Peter Delevoryas [this message]
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=9D98FD36-FA3B-4C9C-A470-69A52FD80677@pjd.dev \
--to=peter@pjd.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sam@mendozajonas.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®