From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: davem@davemloft.net, samuel@sortiz.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 0/4] irda: move it to drivers/staging so we can delete it
Date: Sun, 27 Aug 2017 18:53:37 +0200 [thread overview]
Message-ID: <20170827165337.GA5769@kroah.com> (raw)
In-Reply-To: <1503850759.12569.50.camel@perches.com>
On Sun, Aug 27, 2017 at 09:19:19AM -0700, Joe Perches wrote:
> On Sun, 2017-08-27 at 18:13 +0200, Greg Kroah-Hartman wrote:
> > On Sun, Aug 27, 2017 at 08:35:43AM -0700, Joe Perches wrote:
> > > On Sun, 2017-08-27 at 17:03 +0200, Greg Kroah-Hartman wrote:
> > > > The IRDA code has long been obsolete and broken. So, to keep people
> > > > from trying to use it, and to prevent people from having to maintain it,
> > > > let's move it to drivers/staging/ so that we can delete it entirely from
> > > > the kernel in a few releases.
> > >
> > >
> > > MAINTAINERS should be updated as well.
> > >
> > > It'd probably be nice to try to get an email to
> > > the irda mailing list too if it still works.
> >
> > As get_maintainer.pl didn't show it, odds are it doesn't...
>
> get_maintainer doesn't show it because it's subscriber-only.
> If you want get_maintainer to show it, add -s
>
> $ ./scripts/get_maintainer.pl -s -f net/irda/
> Samuel Ortiz <samuel@sortiz.org> (maintainer:IRDA SUBSYSTEM)
> "David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING [GENERAL])
> irda-users@lists.sourceforge.net (subscriber list:IRDA SUBSYSTEM)
> netdev@vger.kernel.org (open list:IRDA SUBSYSTEM)
> linux-kernel@vger.kernel.org (open list)
Sorry, am not going to subscribe to a random list just to send patches
that delete the subsystem :)
netdev@ should be all that is needed here anyway...
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-27 16:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 15:03 [PATCH 0/4] irda: move it to drivers/staging so we can delete it Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 1/4] irda: move net/irda/ to drivers/staging/irda/net/ Greg Kroah-Hartman
2017-08-30 6:04 ` [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel kernel test robot
2017-08-30 6:12 ` Greg Kroah-Hartman
2017-08-30 6:19 ` Ye Xiaolong
2017-08-27 15:03 ` [PATCH 2/4] irda: move drivers/net/irda to drivers/staging/irda/drivers Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 3/4] irda: move include/net/irda into staging subdirectory Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 4/4] staging: irda: add a TODO file Greg Kroah-Hartman
2017-08-27 15:35 ` [PATCH 0/4] irda: move it to drivers/staging so we can delete it Joe Perches
2017-08-27 16:13 ` Greg Kroah-Hartman
2017-08-27 16:19 ` Joe Perches
2017-08-27 16:53 ` Greg Kroah-Hartman [this message]
2017-08-27 23:15 ` Joe Perches
2017-08-28 23:42 ` David Miller
2017-08-28 23:46 ` Joe Perches
2017-08-29 5:06 ` Greg KH
2017-08-29 21:32 ` Ondrej Zary
2017-08-31 4:30 ` Greg KH
2017-08-31 7:31 ` Ondrej Zary
2017-08-29 10:59 ` Geert Uytterhoeven
2017-08-29 11:11 ` Stefano Brivio
2017-08-29 11:28 ` Greg Kroah-Hartman
2017-08-29 12:11 ` Geert Uytterhoeven
2017-08-29 14:48 ` Greg Kroah-Hartman
2017-08-29 16:49 ` David Miller
2017-08-29 16:38 ` David Miller
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=20170827165337.GA5769@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.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).