From: patchwork-bot+chrome-platform@kernel.org
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: bleung@chromium.org, tzungbi@kernel.org,
chrome-platform@lists.linux.dev, arnd@kernel.org,
hca@linux.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] platform: Handle HAS_IOPORT dependencies
Date: Mon, 08 Apr 2024 06:20:26 +0000 [thread overview]
Message-ID: <171255722609.606.5030818566698111967.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240405134151.5560-1-schnelle@linux.ibm.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Fri, 5 Apr 2024 15:41:50 +0200 you wrote:
> Hi Benson, Tzung-Bi,
>
> 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:
- [1/1] platform: add HAS_IOPORT dependencies
https://git.kernel.org/chrome-platform/c/3b89336c9ccf
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 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 13:41 [PATCH 0/1] platform: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-05 13:41 ` [PATCH 1/1] platform: add " Niklas Schnelle
2024-04-08 6:16 ` Tzung-Bi Shih
2024-04-08 6:20 ` [PATCH 0/1] platform: Handle " patchwork-bot+chrome-platform
2024-04-08 6:20 ` patchwork-bot+chrome-platform [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=171255722609.606.5030818566698111967.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=arnd@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=tzungbi@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 read-only IMAP folder(s) and NNTP newsgroup(s).