From: Greg KH <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: kvalo@codeaurora.org, chunkeey@googlemail.com,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] wireless: move prism54 out to staging
Date: Thu, 3 Aug 2017 17:42:15 -0700 [thread overview]
Message-ID: <20170804004215.GA26035@kroah.com> (raw)
In-Reply-To: <20170803235937.8604-2-mcgrof@kernel.org>
On Thu, Aug 03, 2017 at 04:59:36PM -0700, Luis R. Rodriguez wrote:
> prism54 is deprecated in favor of the p54pci device driver. Although
> only *one soul* had reported issues with it long ago Linux most Linux
> distributions these days just disable the device driver given the
> conflicts with the PCI IDs of p54pci and the *very* unlikely situation
> of folks really need this driver anymore.
>
> Before trying to due away with prism54 once more stuff it into staging,
> which is our hospice for dying drivers.
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
> ---
> MAINTAINERS | 4 ++--
> drivers/net/wireless/intersil/Kconfig | 20 --------------------
> drivers/net/wireless/intersil/Makefile | 1 -
> drivers/staging/Kconfig | 2 ++
> drivers/staging/Makefile | 1 +
Can I get a TODO file that says it will be deleted in a kernel release
or two so don't worry about touching anything in these files?
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-04 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 23:59 [PATCH 0/2] wireless: move prism54 to staging Luis R. Rodriguez
2017-08-03 23:59 ` [PATCH 1/2] wireless: move prism54 out " Luis R. Rodriguez
2017-08-04 0:42 ` Greg KH [this message]
2017-08-04 16:07 ` Luis R. Rodriguez
2017-08-04 6:32 ` Kalle Valo
2017-08-03 23:59 ` [PATCH 2/2] MAINTAINERS: update email address for mcgrof for few straggling drivers Luis R. Rodriguez
2017-08-04 6:31 ` [PATCH 0/2] wireless: move prism54 to staging 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=20170804004215.GA26035@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chunkeey@googlemail.com \
--cc=devel@driverdev.osuosl.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 NNTP newsgroup(s).