public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Florian Fainelli <ffainelli@freebox.fr>
Cc: lkml <linux-kernel@vger.kernel.org>, Maxime Bizon <mbizon@freebox.fr>
Subject: Re: [PATCH] TTY: export NR_LDISC and N_* line discipline numbers to user-space
Date: Tue, 24 May 2011 05:40:44 -0700	[thread overview]
Message-ID: <20110524124044.GD31517@suse.de> (raw)
In-Reply-To: <201105241043.03347.ffainelli@freebox.fr>

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?

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?

Meaning, why has it taken this long for anyone to notice?

thanks,

greg k-h

  reply	other threads:[~2011-05-24 12:57 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 [this message]
2011-05-24 13:17   ` Florian Fainelli
2011-05-24 13:33     ` Greg KH
2011-05-24 13:45       ` Florian Fainelli
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=20110524124044.GD31517@suse.de \
    --to=gregkh@suse.de \
    --cc=ffainelli@freebox.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbizon@freebox.fr \
    /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