From: patchwork-bot+netdevbpf@kernel.org
To: Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Remove some dead code in the Renesas Ethernet drivers
Date: Mon, 31 Jan 2022 11:50:09 +0000 [thread overview]
Message-ID: <164362980941.13015.9613384188127281317.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220129115517.11891-1-s.shtylyov@omp.ru>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 29 Jan 2022 14:55:15 +0300 you wrote:
> Here are 2 patches against DaveM's 'net-next.git' repo. The Renesas drivers
> call their ndo_stop() methods directly and they always return 0, making the
> result checks pointless, hence remove them...
>
> Sergey Shtylyov (2):
> ravb: ravb_close() always returns 0
> sh_eth: sh_eth_close() always returns 0
>
> [...]
Here is the summary with links:
- [v2,1/2] ravb: ravb_close() always returns 0
https://git.kernel.org/netdev/net-next/c/be94a51f3e5e
- [v2,2/2] sh_eth: sh_eth_close() always returns 0
https://git.kernel.org/netdev/net-next/c/e7d966f9ea52
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:[~2022-01-31 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 11:55 [PATCH v2 0/2] Remove some dead code in the Renesas Ethernet drivers Sergey Shtylyov
2022-01-29 11:55 ` [PATCH v2 1/2] ravb: ravb_close() always returns 0 Sergey Shtylyov
2022-02-01 8:55 ` Geert Uytterhoeven
2022-01-29 11:55 ` [PATCH v2 2/2] sh_eth: sh_eth_close() " Sergey Shtylyov
2022-02-01 8:58 ` Geert Uytterhoeven
2022-02-02 14:57 ` Sergei Shtylyov
2022-01-31 11:50 ` 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=164362980941.13015.9613384188127281317.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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).