From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: vt6656: Remove unused 5GHz support
Date: Mon, 14 Mar 2022 18:35:39 +0100 [thread overview]
Message-ID: <Yi9868MQr4CQLgIV@kroah.com> (raw)
In-Reply-To: <cover.1646935331.git.philipp.g.hortmann@gmail.com>
On Thu, Mar 10, 2022 at 07:54:02PM +0100, Philipp Hortmann wrote:
> vt6655 (PCI) and vt6656 (USB) do only support 2.4GHz band and not 5GHz band.
> Both drivers do allow only one vendor id and device id.
> So no other devices are covered by those drivers.
> Because of this the following priv->rf_type cannot occure:
> RF_AIROHA7230
> RF_VT3342A0
>
> ---
> Tested with vt6656 on mini PCIe card (connected over USB)
> which is using rf_type: RF_VT3226D0 (2.4GHz only)
> Tested with vt6656 as USB Plugin Module
> which is using rf_type: RF_AL2230S (2.4GHz only)
> In order to combine vt665x infrastructure it is important
> that vt6655 is also not using this code. (Patch already provided)
> vt6655 on mini PCI Module is using
> rf_type: RF_AIROHA (2.4GHz only)
>
> Philipp Hortmann (5):
> staging: vt6656: Remove unused rf_type in channel.c
> staging: vt6656: Remove unused rf_type in baseband.c
> staging: vt6656: Remove unused rf_type in rf.c; top level
> staging: vt6656: Remove unused rf_type in rf.c; unused variables
> staging: vt6656: Remove unused rf_type in card.c
>
> drivers/staging/vt6656/baseband.c | 16 +-
> drivers/staging/vt6656/card.c | 16 --
> drivers/staging/vt6656/channel.c | 96 +------
> drivers/staging/vt6656/rf.c | 413 +-----------------------------
> 4 files changed, 10 insertions(+), 531 deletions(-)
>
> --
> 2.25.1
>
>
If you could send follow-on patchs for the kernel test bot warnings,
that would be great.
thanks,
greg k-h
prev parent reply other threads:[~2022-03-14 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 18:54 [PATCH 0/5] staging: vt6656: Remove unused 5GHz support Philipp Hortmann
2022-03-10 18:54 ` [PATCH 1/5] staging: vt6656: Remove unused rf_type in channel.c Philipp Hortmann
2022-03-10 18:54 ` [PATCH 2/5] staging: vt6656: Remove unused rf_type in baseband.c Philipp Hortmann
2022-03-11 16:06 ` kernel test robot
2022-03-10 18:54 ` [PATCH 3/5] staging: vt6656: Remove unused rf_type in rf.c; top level Philipp Hortmann
2022-03-10 18:54 ` [PATCH 4/5] staging: vt6656: Remove unused rf_type in rf.c; unused variables Philipp Hortmann
2022-03-10 18:54 ` [PATCH 5/5] staging: vt6656: Remove unused rf_type in card.c Philipp Hortmann
2022-03-10 21:30 ` kernel test robot
2022-03-14 17:35 ` Greg Kroah-Hartman [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=Yi9868MQr4CQLgIV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.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 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.