All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, pabeni@redhat.com, netdev@vger.kernel.org,
	khalasa@piap.pl, asj@cban.com, bbraun@vix.com, explorer@vix.com,
	matt@3am-software.com, arnd@kernel.org,
	tsbogend@alpha.franken.de, linux-mips@vger.kernel.org,
	linus.walleij@linaro.org
Subject: Re: [PATCH net-next] net: wan: remove the lanmedia (lmc) driver
Date: Wed, 06 Apr 2022 14:30:13 +0000	[thread overview]
Message-ID: <164925541346.21938.8264132794493725230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220406041548.643503-1-kuba@kernel.org>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue,  5 Apr 2022 21:15:48 -0700 you wrote:
> The driver for LAN Media WAN interfaces spews build warnings on
> microblaze. The virt_to_bus() calls discard the volatile keyword.
> The right thing to do would be to migrate this driver to a modern
> DMA API but it seems unlikely anyone is actually using it.
> There had been no fixes or functional changes here since
> the git era begun.
> 
> [...]

Here is the summary with links:
  - [net-next] net: wan: remove the lanmedia (lmc) driver
    https://git.kernel.org/netdev/net-next/c/a5b116a0fa90

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-04-06 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  4:15 [PATCH net-next] net: wan: remove the lanmedia (lmc) driver Jakub Kicinski
2022-04-06  7:48 ` Arnd Bergmann
2022-04-06 11:11 ` Thomas Bogendoerfer
2022-04-06 11:46 ` Krzysztof Hałasa
2022-04-06 14: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=164925541346.21938.8264132794493725230.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arnd@kernel.org \
    --cc=asj@cban.com \
    --cc=bbraun@vix.com \
    --cc=davem@davemloft.net \
    --cc=explorer@vix.com \
    --cc=khalasa@piap.pl \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=matt@3am-software.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tsbogend@alpha.franken.de \
    /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.