All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Jiri Slaby <jirislaby@kernel.org>, Jann Horn <jannh@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: Remove dead termiox code
Date: Mon, 7 Dec 2020 14:57:15 +0100	[thread overview]
Message-ID: <X840u5K1Y2kIHnQR@kroah.com> (raw)
In-Reply-To: <20201207101904.GC2265@angband.pl>

On Mon, Dec 07, 2020 at 11:19:04AM +0100, Adam Borowski wrote:
> On Fri, Dec 04, 2020 at 10:10:16AM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 04, 2020 at 09:51:07AM +0100, Jiri Slaby wrote:
> > > > > > On Fri, Dec 04, 2020 at 08:22:41AM +0100, Jiri Slaby wrote:
> > > > > > > On 03. 12. 20, 3:03, Jann Horn wrote:
> > > > > > > > Delete this dead code; but leave the definition of struct termiox in the
> > > > > > > > UAPI headers intact.
> [was snipped]
> > > > > > > I am thinking -- can/should we mark the structure as deprecated so that                                 
> > > > > > > userspace stops using it eventually?   
> 
> > > Note this ^^^^^. He is talking about _not_ touching the definition in the
> > > UAPI header. Does the rest below makes more sense now?
> > 
> > No, I'm still confused :)
> > 
> > We can't touch the UAPI definitions, but the fact that this api never
> > did anything still is ok as after this patch it continues to not do
> > anything.
> > 
> > I'm confused as to what you are proposing...
> 
> The UAPI definition can't be removed, but it would be nice to issue a
> compiler _warning_ if it's ever used.
> 
> Like eg. __attribute__ ((deprecated))

Don't add build warnings for no good reasons, that's not nice.  As the
feature just doesn't work, anyone who tries to use it will very quickly
realize that :)

thanks,

greg k-h

  reply	other threads:[~2020-12-07 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  2:03 [PATCH] tty: Remove dead termiox code Jann Horn
2020-12-03 18:43 ` Greg Kroah-Hartman
2020-12-04  7:22 ` Jiri Slaby
2020-12-04  8:17   ` Greg Kroah-Hartman
2020-12-04  8:20     ` Jiri Slaby
2020-12-04  8:36       ` Greg Kroah-Hartman
2020-12-04  8:51         ` Jiri Slaby
2020-12-04  9:10           ` Greg Kroah-Hartman
2020-12-07 10:19             ` Adam Borowski
2020-12-07 13:57               ` Greg Kroah-Hartman [this message]
2020-12-08 11:13       ` Christoph Hellwig
2020-12-08 11:23         ` Jiri Slaby

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=X840u5K1Y2kIHnQR@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=jirislaby@kernel.org \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.