linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] do not export /usr/include/scsi in make headers_install
Date: Mon, 6 Aug 2007 15:02:10 +0200	[thread overview]
Message-ID: <20070806130210.GA2239@suse.de> (raw)
In-Reply-To: <20070806125212.GB12896@infradead.org>

On Mon, Aug 06, Christoph Hellwig wrote:

> On Mon, Aug 06, 2007 at 02:45:46PM +0200, Olaf Hering wrote:
> > 
> > glibc and make headers_install_all provide /usr/include/scsi
> > One of them has to go.
> > 
> > A quick diff shows no differences, expect:
> 
> ..
> 
> > Which copy should be provided by a distributor?
> 
> The glibc one of course.  The kernel scsi.h should never have been
> added to the list of exportable headers.  

/usr/include/scsi is provided by glibc.
Remove the scsi export from make headers_install target.


Signed-off-by: Olaf Hering <olh@suse.de>

---
 include/Kbuild      |    1 -
 include/scsi/Kbuild |    4 ----
 2 files changed, 5 deletions(-)

--- a/include/Kbuild
+++ b/include/Kbuild
@@ -1,6 +1,5 @@
 header-y += asm-generic/
 header-y += linux/
-header-y += scsi/
 header-y += sound/
 header-y += mtd/
 header-y += rdma/
--- a/include/scsi/Kbuild
+++ /dev/null
@@ -1,4 +0,0 @@
-header-y += scsi.h
-
-unifdef-y += scsi_ioctl.h
-unifdef-y += sg.h

  reply	other threads:[~2007-08-06 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 12:45 glibc and make headers_install_all provide /usr/include/scsi Olaf Hering
2007-08-06 12:52 ` Christoph Hellwig
2007-08-06 13:02   ` Olaf Hering [this message]
2007-08-11  6:42     ` [PATCH] do not export /usr/include/scsi in make headers_install David Woodhouse

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=20070806130210.GA2239@suse.de \
    --to=olh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).