From: Arnd Bergmann <arnd@arndb.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, Karsten Keil <isdn@linux-pingi.de>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging
Date: Wed, 04 Jan 2017 00:03:52 +0100 [thread overview]
Message-ID: <10507790.a4n3csIkKa@wuerfel> (raw)
In-Reply-To: <1483484256.13649.13.camel@tiscali.nl>
On Tuesday, January 3, 2017 11:57:36 PM CET Paul Bolle wrote:
> On Tue, 2017-01-03 at 23:25 +0100, Arnd Bergmann wrote:
> > As far as I'm concerned, we are totally fine as long as there exists a
> > longterm supported kernel that has i4l in drivers/staging.
>
> Or in drivers/isdn, right?
Right, I was assuming that we would first move it to staging and then
delete it, both at future points in time that we can debate. With the
existing longterm kernels that have i4l in drivers/isdn, the few remaining
users still have access to a supported kernel release until at least
2020.
Arnd
next prev parent reply other threads:[~2017-01-03 23:04 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
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 [this message]
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=10507790.a4n3csIkKa@wuerfel \
--to=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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 \
--cc=pebolle@tiscali.nl \
/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).