From: patchwork-bot+netdevbpf@kernel.org
To: Volodymyr Mytnyk <volodymyr.mytnyk@plvision.eu>
Cc: netdev@vger.kernel.org, taras.chornyi@plvision.eu,
mickeyr@marvell.com, serhiy.pshyk@plvision.eu, andrew@lunn.ch,
arnd@arndb.de, geert@linux-m68k.org, dkirjanov@suse.de,
linux@roeck-us.net, vmytnyk@marvell.com, tchornyi@marvell.com,
davem@davemloft.net, kuba@kernel.org, vkochan@marvell.com,
yevhen.orlov@plvision.eu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4] net: marvell: prestera: fix hw structure laid out
Date: Sun, 07 Nov 2021 19:40:07 +0000 [thread overview]
Message-ID: <163631400786.18215.4158190574888211586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1636130964-21252-1-git-send-email-volodymyr.mytnyk@plvision.eu>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 5 Nov 2021 18:49:24 +0200 you wrote:
> From: Volodymyr Mytnyk <vmytnyk@marvell.com>
>
> The prestera FW v4.0 support commit has been merged
> accidentally w/o review comments addressed and waiting
> for the final patch set to be uploaded. So, fix the remaining
> comments related to structure laid out and build issues.
>
> [...]
Here is the summary with links:
- [net,v4] net: marvell: prestera: fix hw structure laid out
https://git.kernel.org/netdev/net/c/e1464db5c57e
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-11-07 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 16:49 [PATCH net v4] net: marvell: prestera: fix hw structure laid out Volodymyr Mytnyk
2021-11-05 20:14 ` Guenter Roeck
2021-11-05 22:42 ` Volodymyr Mytnyk
2021-11-06 8:42 ` Geert Uytterhoeven
2021-11-06 10:54 ` Volodymyr Mytnyk
2021-11-07 19:40 ` 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=163631400786.18215.4158190574888211586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=dkirjanov@suse.de \
--cc=geert@linux-m68k.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mickeyr@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=serhiy.pshyk@plvision.eu \
--cc=taras.chornyi@plvision.eu \
--cc=tchornyi@marvell.com \
--cc=vkochan@marvell.com \
--cc=vmytnyk@marvell.com \
--cc=volodymyr.mytnyk@plvision.eu \
--cc=yevhen.orlov@plvision.eu \
/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.