From: patchwork-bot+netdevbpf@kernel.org
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: arnd@kernel.org, m.grzeschik@pengutronix.de,
netdev@vger.kernel.org, hca@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
edumazet@google.com, mkl@pengutronix.de,
linux-hams@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
pabeni@redhat.com, davem@davemloft.net,
mailhol.vincent@wanadoo.fr
Subject: Re: [Intel-wired-lan] [PATCH net-next 0/1] XYZ: Handle HAS_IOPORT dependencies
Date: Mon, 08 Apr 2024 11:00:34 +0000 [thread overview]
Message-ID: <171257403468.26748.18118428857352948104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405111831.3881080-1-schnelle@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 5 Apr 2024 13:18:30 +0200 you wrote:
> Hi networking maintainers,
>
> This is a follow up in my ongoing effort of making inb()/outb() and
> similar I/O port accessors compile-time optional. Previously I sent this
> as a treewide series titled "treewide: Remove I/O port accessors for
> HAS_IOPORT=n" with the latest being its 5th version[0]. With a significant
> subset of patches merged I've changed over to per-subsystem series. These
> series are stand alone and should be merged via the relevant tree such
> that with all subsystems complete we can follow this up with the final
> patch that will make the I/O port accessors compile-time optional.
>
> [...]
Here is the summary with links:
- [net-next,1/1] net: handle HAS_IOPORT dependencies
https://git.kernel.org/netdev/net-next/c/a29689e60ed3
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:[~2024-04-08 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:18 [Intel-wired-lan] [PATCH net-next 0/1] XYZ: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-05 11:18 ` [Intel-wired-lan] [PATCH net-next 1/1] net: handle " Niklas Schnelle
2024-04-05 11:21 ` [Intel-wired-lan] [PATCH net-next 0/1] XYZ: Handle " Niklas Schnelle
2024-04-08 11:00 ` 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=171257403468.26748.18118428857352948104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hca@linux.ibm.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=schnelle@linux.ibm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).