linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Karsten Keil <isdn@linux-pingi.de>,
	linux-arm-kernel@lists.infradead.org,
	Jonathan Corbet <corbet@lwn.net>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging
Date: Tue, 3 Jan 2017 16:24:36 +0100	[thread overview]
Message-ID: <20170103152436.GA26156@kroah.com> (raw)
In-Reply-To: <1456945629-1793533-2-git-send-email-arnd@arndb.de>

On Wed, Mar 02, 2016 at 08:06:46PM +0100, Arnd Bergmann wrote:
> The icn, act2000 and pcbit drivers are all for very old hardware,
> and it is highly unlikely that anyone is actually still using them
> on modern kernels, if at all.
> 
> All three drivers apparently are for hardware that predates PCI
> being the common connector, as they are ISA-only and active
> PCI ISDN cards were widely available in the 1990s.
> 
> Looking through the git logs, it I cannot find any indication of a
> patch to any of these drivers that has been tested on real hardware,
> only cleanups or global API changes.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Acked-by: Karsten Keil <isdn@linux-pingi.de>

This patch got added in the 4.6 kernel release.  As I am now taking
patches for 4.11-rc1, I figure it is time to just delete the
drivers/staging/i4l/ directory now, given that no one has really done
anything with it.  If people show up that wish to maintain it, I'll be
glad to revert it, or if someone really screams in the next week.
Otherwise it's time to just move on :)

thanks,

greg k-h

  parent reply	other threads:[~2017-01-03 15:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 19:06 [PATCH 1/2] isdn: icn: remove a #warning Arnd Bergmann
2016-03-02 19:06 ` [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging Arnd Bergmann
2016-03-03  8:30   ` isdn
2016-03-04 15:24     ` Arnd Bergmann
2016-03-04 16:18       ` Paul Bolle
2016-03-04 16:32         ` Arnd Bergmann
2016-03-07  8:33           ` Paul Bolle
2016-03-05 13:08         ` Tilman Schmidt
2016-03-07  8:48           ` Paul Bolle
2016-03-09 22:10             ` Tilman Schmidt
2016-03-10 10:53               ` isdn
2016-03-10 12:58                 ` Paul Bolle
2016-03-10 16:41                   ` isdn
2016-03-11 20:04                     ` Tilman Schmidt
2016-03-04 18:18       ` isdn
2016-03-04 21:00         ` Arnd Bergmann
2016-03-07  6:57       ` Holger Schurig
2016-03-19 10:27         ` Tilman Schmidt
2016-03-03 22:22   ` David Miller
2016-03-03 22:33     ` Greg KH
2016-03-05  3:19   ` kbuild test robot
2017-01-03 15:24   ` Greg Kroah-Hartman [this message]
2017-01-03 21:19     ` Arnd Bergmann
2017-01-03 21:54       ` Paul Bolle
2017-01-03 22:25         ` Arnd Bergmann
2017-01-03 22:57           ` Paul Bolle
2017-01-03 23:03             ` Arnd Bergmann
2017-01-05 21:19       ` Greg Kroah-Hartman

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=20170103152436.GA26156@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=isdn@linux-pingi.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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).