From: patchwork-bot+netdevbpf@kernel.org
To: Shinas Rasheed <srasheed@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
hgani@marvell.com, vimleshk@marvell.com, egallen@redhat.com,
mschmidt@redhat.com, pabeni@redhat.com, horms@kernel.org,
kuba@kernel.org, davem@davemloft.net, wizhao@redhat.com,
konguyen@redhat.com, jesse.brandeburg@intel.com,
sumang@marvell.com
Subject: Re: [PATCH net-next v2 0/2] Get max rx packet length and solve
Date: Fri, 24 Nov 2023 12:20:30 +0000 [thread overview]
Message-ID: <170082843001.28500.952047846301067356.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231122183435.2510656-1-srasheed@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 22 Nov 2023 10:34:33 -0800 you wrote:
> Patchsets which resolve observed style issues in control net
> source files, and also implements get mtu control net api
> to fetch max mtu value from firmware
>
> Changes:
> V2:
> - Introduced a patch to resolve style issues as mentioned in V1
> - Removed OCTEP_MAX_MTU macro, as it is redundant.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] octeon_ep: Solve style issues in control net files
https://git.kernel.org/netdev/net-next/c/e40f4c4e50fc
- [net-next,v2,2/2] octeon_ep: get max rx packet length from firmware
https://git.kernel.org/netdev/net-next/c/0a5f8534e398
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:[~2023-11-24 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 18:34 [PATCH net-next v2 0/2] Get max rx packet length and solve Shinas Rasheed
2023-11-22 18:34 ` [PATCH net-next v2 1/2] octeon_ep: Solve style issues in control net files Shinas Rasheed
2023-11-22 18:34 ` [PATCH net-next v2 2/2] octeon_ep: get max rx packet length from firmware Shinas Rasheed
2023-11-24 17:08 ` Simon Horman
2023-11-27 4:43 ` [EXT] " Shinas Rasheed
2023-11-24 12:20 ` 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=170082843001.28500.952047846301067356.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=srasheed@marvell.com \
--cc=sumang@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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).