From: Patrick Williams <patrick@stwcx.xyz>
To: Ivan Mikhaylov <fr0st61te@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, peter@pjd.dev, sam@mendozajonas.com
Subject: Re: [PATCH net-next v2 3/3] net/ncsi: Add NC-SI 1.2 Get MC MAC Address command
Date: Sun, 10 Dec 2023 20:50:56 -0600 [thread overview]
Message-ID: <ZXZ5EOSJAekCiT44@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <20231210215356.4154-1-fr0st61te@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
On Mon, Dec 11, 2023 at 12:53:56AM +0300, Ivan Mikhaylov wrote:
>
> seems very similar to ncsi_rsp_handler_oem_gma except address_count, why it
> shouldn't be part of this call with additional param? What's inside it just
> code duplicity of ncsi_rsp_handler_oem_gma.
>
> And as we talked in openbmc mailing list, ndo_set_mac_address do not notify
> network layer about mac change and this fixed part already in
> ncsi_rsp_handler_oem_gma with 790071347a0a1a89e618eedcd51c687ea783aeb3 .
>
> David, any actions should be needed about fixing it in net-next? Need it to
> put patch above with fix or do the revert from net-next and make it right?
I agree that both of your recommendations might make the code better,
but I don't see why we would need to revert it. The code does the
intended function for many use cases, even if you've identified a few
where calling `dev_set_mac_address` would be better.
Either you or I can send a "Fixes: " on this commit to improve the
handling as you're proposing. While the change is likely trivial, I
have not had any chance to test it yet, so I've not sent it up myself.
If you want to refactor the code to reduce duplication, I think that should
be an entirely separate proposal.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-11 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:07 [PATCH net-next v2 0/3] net/ncsi: Add NC-SI 1.2 Get MC MAC Address command Patrick Williams
2023-11-14 16:07 ` [PATCH net-next v2 1/3] net/ncsi: Simplify Kconfig/dts control flow Patrick Williams
2023-11-14 16:07 ` [PATCH net-next v2 2/3] net/ncsi: Fix netlink major/minor version numbers Patrick Williams
2023-11-14 16:07 ` [PATCH net-next v2 3/3] net/ncsi: Add NC-SI 1.2 Get MC MAC Address command Patrick Williams
2023-12-10 21:53 ` Ivan Mikhaylov
2023-12-11 2:50 ` Patrick Williams [this message]
2023-12-11 16:51 ` Jakub Kicinski
2023-11-18 15:10 ` [PATCH net-next v2 0/3] " patchwork-bot+netdevbpf
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=ZXZ5EOSJAekCiT44@heinlein.vulture-banana.ts.net \
--to=patrick@stwcx.xyz \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fr0st61te@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter@pjd.dev \
--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;
as well as URLs for NNTP newsgroup(s).