public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jiri Slaby <jslaby@suse.cz>, Arnd Bergmann <arnd@arndb.de>,
	Paul Bolle <pebolle@tiscali.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] delete seven tty headers
Date: Mon, 11 Jun 2012 16:42:04 -0700	[thread overview]
Message-ID: <20120611234204.GA17383@kroah.com> (raw)
In-Reply-To: <20120611234033.GB17313@kroah.com>

On Mon, Jun 11, 2012 at 04:40:33PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Jun 11, 2012 at 01:53:06PM +0100, Alan Cox wrote:
> > > I agree (I wrote I doubt there are any users at all). But I would prefer
> > > going through the deprecation phase (adding a #warning) anyway. Removing
> > > the headers completely in a year, or maybe sooner is OK then.
> > 
> > I really see no point. Distributions are going to build against a set of
> > headers generated from a kernel, once at the time the distribution is
> > first assembled (eg the kernel-headers package in Fedora).
> 
> I agree, I'll take this patch now as the drivers are gone, the headers
> should be as well.

Although, as this originally happened in 3.1, I think it's safe to wait
for 3.6 for this patch to go in, no rush for 3.5.

thanks,

greg k-h

      reply	other threads:[~2012-06-11 23:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  8:56 [PATCH] delete seven tty headers Paul Bolle
2012-06-08  9:19 ` Alan Cox
2012-06-08 11:00 ` Jiri Slaby
2012-06-08 11:41   ` Paul Bolle
2012-06-08 14:03     ` Arnd Bergmann
2012-06-11 12:42       ` Jiri Slaby
2012-06-11 12:53         ` Alan Cox
2012-06-11 23:40           ` Greg Kroah-Hartman
2012-06-11 23:42             ` 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=20120611234204.GA17383@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@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