From: Simon Horman <horms@kernel.org>
To: Karthik Sundaravel <ksundara@redhat.com>
Cc: jesse.brandeburg@intel.com, wojciech.drewek@intel.com,
sumang@marvell.com, jacob.e.keller@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pmenzel@molgen.mpg.de,
jiri@resnulli.us, michal.swiatkowski@linux.intel.com,
rjarry@redhat.com, aharivel@redhat.com, vchundur@redhat.com,
cfontain@redhat.com
Subject: Re: [PATCH v8] ice: Add get/set hw address for VFs using devlink commands
Date: Mon, 8 Apr 2024 14:27:32 +0100 [thread overview]
Message-ID: <20240408132732.GH26556@kernel.org> (raw)
In-Reply-To: <20240404075917.4347-2-ksundara@redhat.com>
On Thu, Apr 04, 2024 at 01:29:17PM +0530, Karthik Sundaravel wrote:
> Changing the MAC address of the VFs is currently unsupported via devlink.
> Add the function handlers to set and get the HW address for the VFs.
>
> Signed-off-by: Karthik Sundaravel <ksundara@redhat.com>
Hi Karthik,
I think this series should be targeted at iwl-next [1]
but it does not seem to apply against the dev-queue branch of
that tree (or net-next).
Please consider rebasing and reposting with the target tree specified
in the subject. e.g.
Subject: [PATCH iwl-next v9] ...
[1] https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git
Otherwise the patch looks good to me.
prev parent reply other threads:[~2024-04-08 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 7:59 [PATCH v8] ice: Add get/set hw address for VFs using devlink commands Karthik Sundaravel
2024-04-04 7:59 ` Karthik Sundaravel
2024-04-08 13:27 ` Simon Horman [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=20240408132732.GH26556@kernel.org \
--to=horms@kernel.org \
--cc=aharivel@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=cfontain@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=ksundara@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=rjarry@redhat.com \
--cc=sumang@marvell.com \
--cc=vchundur@redhat.com \
--cc=wojciech.drewek@intel.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).