From: Kalle Valo <kvalo@kernel•org>
To: Niklas Schnelle <schnelle@linux•ibm.com>
Cc: Arnd Bergmann <arnd@arndb•de>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
linux-kernel@vger•kernel.org, linux-arch@vger•kernel.org,
linux-pci@vger•kernel.org, Arnd Bergmann <arnd@kernel•org>,
"David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Jouni Malinen <j@w1•fi>,
linux-wireless@vger•kernel.org (open list:NETWORKING DRIVERS
(WIRELESS)),
netdev@vger•kernel.org (open list:NETWORKING DRIVERS)
Subject: Re: [RFC v2 38/39] wireless: add HAS_IOPORT dependencies
Date: Fri, 29 Apr 2022 17:40:53 +0300 [thread overview]
Message-ID: <87zgk4c5qi.fsf@kernel.org> (raw)
In-Reply-To: <20220429135108.2781579-70-schnelle@linux.ibm.com> (Niklas Schnelle's message of "Fri, 29 Apr 2022 15:51:07 +0200")
Niklas Schnelle <schnelle@linux•ibm.com> writes:
> In a future patch HAS_IOPORT=n will result in inb()/outb() and friends
> not being declared. We thus need to add HAS_IOPORT as dependency for
> those drivers using them.
>
> Co-developed-by: Arnd Bergmann <arnd@kernel•org>
> Signed-off-by: Niklas Schnelle <schnelle@linux•ibm.com>
I assume this will go via some other tree than wireless-next:
Acked-by: Kalle Valo <kvalo@kernel•org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-04-29 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220429135108.2781579-1-schnelle@linux.ibm.com>
2022-04-29 13:50 ` [RFC v2 19/39] mISDN: add HAS_IOPORT dependencies Niklas Schnelle
2022-04-29 13:50 ` [PATCH 20/37] net: " Niklas Schnelle
2022-04-29 14:33 ` Niklas Schnelle
2022-04-29 13:50 ` [RFC v2 21/39] " Niklas Schnelle
2022-04-29 14:13 ` Marc Kleine-Budde
2022-05-01 22:48 ` Maciej W. Rozycki
2022-05-03 12:45 ` Niklas Schnelle
2022-05-03 13:36 ` Maciej W. Rozycki
2022-04-29 13:51 ` [RFC v2 38/39] wireless: " Niklas Schnelle
2022-04-29 14:40 ` Kalle Valo [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=87zgk4c5qi.fsf@kernel.org \
--to=kvalo@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=arnd@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=j@w1$(echo .)fi \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=schnelle@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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