public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <ffainelli@freebox.fr>
To: Greg KH <gregkh@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Maxime Bizon <mbizon@freebox.fr>, Tilman Schmidt <tilman@imap.cc>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] TTY: export NR_LDISC and N_* line discipline numbers to user-space
Date: Tue, 24 May 2011 15:45:08 +0200	[thread overview]
Message-ID: <201105241545.08288.ffainelli@freebox.fr> (raw)
In-Reply-To: <20110524133353.GB19488@suse.de>

On Tuesday 24 May 2011 15:33:53 Greg KH wrote:
> On Tue, May 24, 2011 at 03:17:23PM +0200, Florian Fainelli wrote:
> > Hello,
> > 
> > On Tuesday 24 May 2011 14:40:44 Greg KH wrote:
> > > On Tue, May 24, 2011 at 10:43:03AM +0200, Florian Fainelli wrote:
> > > > From: Florian Fainelli <ffainelli@freebox.fr>
> > > > 
> > > > Since commit (4564f9e5: consolidate line discipline number
> > > > definitions) the patch moved all line discipline number from a
> > > > per-architecture termios.h to a shared one: tty.h. However, prior to
> > > > this consolidation work, the line discipline numbers were outside of
> > > > an ifdef
> > > > __KERNEL__/endif block so these numbers used to be exported to
> > > > user-space.
> > > > 
> > > > Since such numbers are kernel ABI anyway, and tty.h is already
> > > > included for user- space header processing, just move these relevant
> > > > defines outside of the ifdef __KERNEL__/endif block in
> > > > include/linux/tty.h.
> > > 
> > > Any reason you didn't copy _any_ of the people who signed off on that
> > > patch, or the original author of that patch?
> > 
> > No particular reason but my mistake, fixed that.
> > 
> > > Anyway, this is been this way for four years, since the 2.6.21 kernel
> > > release.  Since no one has noticed, or complained, since then, how much
> > > a problem is this really?
> > 
> > This is a problem because you may have out of tree drivers using a line
> > discpline number, and you do not want your companion user-space
> > application to have to use a different line discpline number but the one
> > the kernel should provide.
> > 
> > > Meaning, why has it taken this long for anyone to notice?
> > 
> > - long standing user-space applications such as pppd got their N_PPP long
> > ago, and do not have to worry about N_PPP being renumbered so they can
> > just define it in pppd's sources it won't break
> > 
> > - I started implementing a line discipline driver only a couple of months
> > ago and then realized that such ABI should have been exported
> 
> Ok, then it really isn't that important of a change :)
> 
> I'll queue it up for the next major merge window after this one, thanks.

Thanks!
--
Florian

  reply	other threads:[~2011-05-24 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24  8:43 [PATCH] TTY: export NR_LDISC and N_* line discipline numbers to user-space Florian Fainelli
2011-05-24 12:40 ` Greg KH
2011-05-24 13:17   ` Florian Fainelli
2011-05-24 13:33     ` Greg KH
2011-05-24 13:45       ` Florian Fainelli [this message]
2011-05-24 14:09     ` Tilman Schmidt

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=201105241545.08288.ffainelli@freebox.fr \
    --to=ffainelli@freebox.fr \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbizon@freebox.fr \
    --cc=tilman@imap.cc \
    /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