From: Saeed Mahameed <saeedm@nvidia.com>
To: "kuba@kernel.org" <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] mlx5: don't write directly to netdev->dev_addr
Date: Wed, 20 Oct 2021 17:54:56 +0000 [thread overview]
Message-ID: <d11a744067a3481c37d013a1f770af9b761dd57f.camel@nvidia.com> (raw)
In-Reply-To: <20211013202001.311183-1-kuba@kernel.org>
On Wed, 2021-10-13 at 13:20 -0700, Jakub Kicinski wrote:
> Use a local buffer and eth_hw_addr_set().
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> This takes care of Ethernet, mlx5/core/ipoib/ipoib.c
> will be changed as part of all the IB conversions.
>
Hi Jakub,
the patch looks fine, i will take it directly to net-next-mlx5,
I didn't get the part about IB conversions, where can i find that ?
next prev parent reply other threads:[~2021-10-20 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 20:20 [PATCH] mlx5: don't write directly to netdev->dev_addr Jakub Kicinski
2021-10-20 17:54 ` Saeed Mahameed [this message]
2021-10-20 18:15 ` Jakub Kicinski
2021-10-20 23:41 ` Saeed Mahameed
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=d11a744067a3481c37d013a1f770af9b761dd57f.camel@nvidia.com \
--to=saeedm@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@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).