From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@netronome.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
oss-drivers@netronome.com, yinjun.zhang@corigine.com,
louis.peens@corigine.com
Subject: Re: [PATCH net] nfp: devlink: initialize the devlink port attribute "lanes"
Date: Wed, 21 Apr 2021 17:30:08 +0000 [thread overview]
Message-ID: <161902620892.9844.3758040141120463484.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210421092415.13094-1-simon.horman@netronome.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 21 Apr 2021 11:24:15 +0200 you wrote:
> From: Yinjun Zhang <yinjun.zhang@corigine.com>
>
> The number of lanes of devlink port should be correctly initialized
> when registering the port, so that the input check when running
> "devlink port split <port> count <N>" can pass.
>
> Fixes: a21cf0a8330b ("devlink: Add a new devlink port lanes attribute and pass to netlink")
> Signed-off-by: Yinjun Zhang <yinjun.zhang@corigine.com>
> Signed-off-by: Louis Peens <louis.peens@corigine.com>
> Signed-off-by: Simon Horman <simon.horman@netronome.com>
>
> [...]
Here is the summary with links:
- [net] nfp: devlink: initialize the devlink port attribute "lanes"
https://git.kernel.org/netdev/net/c/90b669d65d99
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-21 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 9:24 [PATCH net] nfp: devlink: initialize the devlink port attribute "lanes" Simon Horman
2021-04-21 17:30 ` patchwork-bot+netdevbpf [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=161902620892.9844.3758040141120463484.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.com \
--cc=yinjun.zhang@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.