From: Kalle Valo <kvalo@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless@vger.kernel.org, toke@toke.dk, nbd@nbd.name
Subject: Re: [PATCH] wireless: ath9k: eeprom: remove platform data
Date: Wed, 04 Sep 2024 11:05:32 +0300 [thread overview]
Message-ID: <87jzfrkfn7.fsf@kernel.org> (raw)
In-Reply-To: <20240903202713.471489-1-rosenp@gmail.com> (Rosen Penev's message of "Tue, 3 Sep 2024 13:27:13 -0700")
Rosen Penev <rosenp@gmail.com> writes:
> There are no more board files defining platform data for this driver and
> eeprom support through NVMEM has already been implemented. No need to
> keep this old functionality around.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> As an aside, the last user of this functionality downstream in OpenWrt
> has been removed: https://github.com/openwrt/openwrt/commit/7ac8279bd
>
> drivers/net/wireless/ath/ath9k/eeprom.c | 12 ------------
> 1 file changed, 12 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/eeprom.c b/drivers/net/wireless/ath/ath9k/eeprom.c
> index efb7889142d4..df58dc02e104 100644
> --- a/drivers/net/wireless/ath/ath9k/eeprom.c
> +++ b/drivers/net/wireless/ath/ath9k/eeprom.c
> @@ -15,7 +15,6 @@
> */
>
> #include "hw.h"
> -#include <linux/ath9k_platform.h>
What about the file include/linux/ath9k_platform.h? That should be also
removed, right?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
https://docs.kernel.org/process/submitting-patches.html
next prev parent reply other threads:[~2024-09-04 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 20:27 [PATCH] wireless: ath9k: eeprom: remove platform data Rosen Penev
2024-09-04 8:05 ` Kalle Valo [this message]
2024-09-04 14:53 ` Jeff Johnson
2024-09-04 17:56 ` Rosen Penev
2024-09-04 23:53 ` Rosen Penev
2024-09-05 5:46 ` Kalle Valo
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=87jzfrkfn7.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=rosenp@gmail.com \
--cc=toke@toke.dk \
/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.