From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?UmFmYcWCIE1pxYJlY2tpIDx6YWplYzVAZ21haWwuY29tPg==?=@ci.codeaurora.org
Cc: davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org,
f.fainelli@gmail.com, rdunlap@infradead.org,
masahiroy@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
rafal@milecki.pl
Subject: Re: [PATCH net-next 5.12 0/8] bcm4908_enet: post-review fixes
Date: Thu, 11 Feb 2021 23:10:15 +0000 [thread overview]
Message-ID: <161308501543.27196.4327749060967319260.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210211121239.728-1-zajec5@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 11 Feb 2021 13:12:31 +0100 you wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> V2 of my BCM4908 Ethernet patchset was applied to the net-next.git and
> it was later that is received some extra reviews. I'm sending patches
> that handle pointed out issues.
>
> David: earler I missed that V2 was applied and I sent V3 and V4 of my
> inital patchset. Sorry for that. I think it's the best to ignore V3 and
> V4 I sent and proceed with this fixes patchset instead.
>
> [...]
Here is the summary with links:
- [net-next,5.12,1/8] dt-bindings: net: rename BCM4908 Ethernet binding
https://git.kernel.org/netdev/net-next/c/6710c5b0674f
- [net-next,5.12,2/8] dt-bindings: net: bcm4908-enet: include ethernet-controller.yaml
https://git.kernel.org/netdev/net-next/c/f08b5cf1eb1f
- [net-next,5.12,3/8] net: broadcom: rename BCM4908 driver & update DT binding
https://git.kernel.org/netdev/net-next/c/9d61d138ab30
- [net-next,5.12,4/8] net: broadcom: bcm4908_enet: drop unneeded memset()
https://git.kernel.org/netdev/net-next/c/af263af64683
- [net-next,5.12,5/8] net: broadcom: bcm4908_enet: drop "inline" from C functions
https://git.kernel.org/netdev/net-next/c/7b778ae4eb9c
- [net-next,5.12,6/8] net: broadcom: bcm4908_enet: fix minor typos
https://git.kernel.org/netdev/net-next/c/e39488117203
- [net-next,5.12,7/8] net: broadcom: bcm4908_enet: fix received skb length
https://git.kernel.org/netdev/net-next/c/195e2d9febfb
- [net-next,5.12,8/8] net: broadcom: bcm4908_enet: fix endianness in xmit code
https://git.kernel.org/netdev/net-next/c/bdd70b997799
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-02-11 23:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 21:44 [PATCH net-next 1/2] dt-bindings: net: document BCM4908 Ethernet controller Rafał Miłecki
2021-02-05 21:44 ` [PATCH net-next 2/2] net: broadcom: bcm4908enet: add BCM4908 controller driver Rafał Miłecki
2021-02-05 23:47 ` kernel test robot
2021-02-07 22:26 ` [PATCH V2 net-next 1/2] dt-bindings: net: document BCM4908 Ethernet controller Rafał Miłecki
2021-02-07 22:26 ` [PATCH V2 net-next 2/2] net: broadcom: bcm4908enet: add BCM4908 controller driver Rafał Miłecki
2021-02-09 23:01 ` [PATCH V3 net-next 1/2] dt-bindings: net: document BCM4908 Ethernet controller Rafał Miłecki
2021-02-09 23:01 ` [PATCH V3 net-next 2/2] net: broadcom: bcm4908_enet: add BCM4908 controller driver Rafał Miłecki
2021-02-10 2:39 ` Andrew Lunn
2021-02-10 7:57 ` Rafał Miłecki
2021-02-10 9:47 ` [PATCH V4 net-next 1/2] dt-bindings: net: document BCM4908 Ethernet controller Rafał Miłecki
2021-02-10 9:47 ` [PATCH V4 net-next 2/2] net: broadcom: bcm4908_enet: add BCM4908 controller driver Rafał Miłecki
2021-02-11 0:44 ` Andrew Lunn
2021-02-11 12:12 ` [PATCH net-next 5.12 0/8] bcm4908_enet: post-review fixes Rafał Miłecki
2021-02-11 12:12 ` [PATCH net-next 5.12 1/8] dt-bindings: net: rename BCM4908 Ethernet binding Rafał Miłecki
2021-02-11 17:44 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 2/8] dt-bindings: net: bcm4908-enet: include ethernet-controller.yaml Rafał Miłecki
2021-02-11 17:44 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 3/8] net: broadcom: rename BCM4908 driver & update DT binding Rafał Miłecki
2021-02-11 17:44 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 4/8] net: broadcom: bcm4908_enet: drop unneeded memset() Rafał Miłecki
2021-02-11 17:45 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 5/8] net: broadcom: bcm4908_enet: drop "inline" from C functions Rafał Miłecki
2021-02-11 17:45 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 6/8] net: broadcom: bcm4908_enet: fix minor typos Rafał Miłecki
2021-02-11 17:46 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 7/8] net: broadcom: bcm4908_enet: fix received skb length Rafał Miłecki
2021-02-11 17:46 ` Florian Fainelli
2021-02-11 12:12 ` [PATCH net-next 5.12 8/8] net: broadcom: bcm4908_enet: fix endianness in xmit code Rafał Miłecki
2021-02-11 17:46 ` Florian Fainelli
2021-02-11 23:10 ` patchwork-bot+netdevbpf [this message]
2021-02-09 21:43 ` [PATCH V2 net-next 1/2] dt-bindings: net: document BCM4908 Ethernet controller Rob Herring
2021-02-09 22:07 ` Rafał Miłecki
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=161308501543.27196.4327749060967319260.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?UmFmYcWCIE1pxYJlY2tpIDx6YWplYzVAZ21haWwuY29tPg==?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=rdunlap@infradead.org \
--cc=robh+dt@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).