From: patchwork-bot+netdevbpf@kernel.org
To: Joel Stanley <joel@jms.id.au>
Cc: davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org,
kgugala@antmicro.com, mholenko@antmicro.com,
devicetree@vger.kernel.org, florent@enjoy-digital.fr,
gsomlo@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] net: Add LiteETH network driver
Date: Thu, 26 Aug 2021 11:30:06 +0000 [thread overview]
Message-ID: <162997740642.22703.3742486992614498379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210825222106.3113287-1-joel@jms.id.au>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 26 Aug 2021 07:51:04 +0930 you wrote:
> This adds a driver for the LiteX network device, LiteEth.
>
> v4 Fixes the bindings and adds r-b tags from Gabriel and Rob.
>
> v3 Updates the bindings to describe the slots in a way that makes more
> sense for the hardware, instead of trying to fit some existing
> properties. The driver is updated to use these bindings, and fix some
> issues pointed out by Gabriel.
>
> [...]
Here is the summary with links:
- [v4,1/2] dt-bindings: net: Add bindings for LiteETH
https://git.kernel.org/netdev/net-next/c/b0f8d3077f8f
- [v4,2/2] net: Add driver for LiteX's LiteETH network interface
https://git.kernel.org/netdev/net-next/c/ee7da21ac4c3
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-08-26 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 22:21 [PATCH v4 0/2] net: Add LiteETH network driver Joel Stanley
2021-08-25 22:21 ` [PATCH v4 1/2] dt-bindings: net: Add bindings for LiteETH Joel Stanley
2021-08-25 22:21 ` [PATCH v4 2/2] net: Add driver for LiteX's LiteETH network interface Joel Stanley
2021-08-26 11: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=162997740642.22703.3742486992614498379.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=florent@enjoy-digital.fr \
--cc=gsomlo@gmail.com \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mholenko@antmicro.com \
--cc=netdev@vger.kernel.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).