public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] delete seven tty headers
Date: Fri, 08 Jun 2012 13:00:00 +0200	[thread overview]
Message-ID: <4FD1DB30.80307@suse.cz> (raw)
In-Reply-To: <1339145808.25798.28.camel@x61.thuisdomein>

On 06/08/2012 10:56 AM, Paul Bolle wrote:
> 0) Tested with "git grep" only (by grepping on the file names). I
> haven't grepped on the many things these headers provide (mostly named
> constants). Some of these looked rather generic. Most of these headers
> were relevant for builds I don't have the toolchains for at hand. And,
> finally, I couldn't think of a way the things these headers provide
> could still actually be used in the tree. 
> 
> But would you prefer further tests?

Nope, it's enough to know nobody in the kernel includes them.

> 1) cdk.h, comstats.h, istallion.h, and stallion.h are still referenced
> in Documentation/ioctl/ioctl-number.txt and
> Documentation/magic-number.txt. Should those references be deleted too?

Yes, please.

> --- a/include/linux/Kbuild
> +++ b/include/linux/Kbuild
> @@ -84,7 +84,6 @@ header-y += capability.h
>  header-y += capi.h
>  header-y += cciss_defs.h
>  header-y += cciss_ioctl.h
> -header-y += cdk.h
>  header-y += cdrom.h
>  header-y += cgroupstats.h
>  header-y += chio.h
> @@ -93,7 +92,6 @@ header-y += cn_proc.h
>  header-y += coda.h
>  header-y += coda_psdev.h
>  header-y += coff.h
> -header-y += comstats.h
>  header-y += connector.h
>  header-y += const.h
>  header-y += cramfs_fs.h

NACK for these two files. I rather prefer going through the
deprecate-wait_years-delete path (removal of __KERNEL__ parts, if there
are any, is OK). I doubt there are any users at all, but we still should
gave them a chance to fix their builds (remove those #include's and
potentially used defined/structs) and not introduce a userspace build
breakage.

The rest is OK to be removed.

thanks,
-- 
js
suse labs



  parent reply	other threads:[~2012-06-08 11:00 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 [this message]
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

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=4FD1DB30.80307@suse.cz \
    --to=jslaby@suse.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --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