public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Smart <James.Smart@Emulex.Com>,
	Andrew Morton <akpm@linux-foundation.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
	Olaf Hering <olh@suse.de>, Sam Ravnborg <sam@ravnborg.org>,
	Benny Halevy <bhalevy@panasas.com>,
	LKML <linux-kernel@vger.kernel.org>,
	scst-devel <scst-devel@lists.sourceforge.net>,
	Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] SCSI: userspace cannot use scsi_command_size_tbl, COMMAND_SIZE and scsi_device_type
Date: Sun, 28 Jun 2009 19:00:38 +0300	[thread overview]
Message-ID: <4A4793A6.8080802@panasas.com> (raw)
In-Reply-To: <4A477F00.70305@emulex.com>

On 06/28/2009 05:32 PM, James Smart wrote:
> Sorry folks --  the nuance of the clibrary having it's own version of a 
> kernel header for distros was completely unknown to me.
> 
> Christoph mentioned this to me last week, with the recommendation to 
> back out the patch and move the other headers that were exprted into 
> include/linux - thus nothing in include/scsi gets export.  No Problem. 
> and I'll do so shortly.
> 
> How does a lowly contributor track these kind of nuances ?
> 
> -- james s
> 

Don't give up so fast. Please. 
Kernel should reclaim back control of it's own headers.
/usr/include/scsi is Kernel territory from the start.
This is just a plain historical mistake that glibc had
to duplicate all these Kernel headers.

Please lets start with scsi.h and then advance slowly
to more Headers like sg.h

Andrew, please help.

Thanks
Boaz

      parent reply	other threads:[~2009-06-28 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27 17:05 [PATCH] SCSI: userspace cannot use scsi_command_size_tbl, COMMAND_SIZE and scsi_device_type Jaswinder Singh Rajput
2009-06-27 17:27 ` James Bottomley
2009-06-27 17:56   ` Jaswinder Singh Rajput
2009-06-27 18:28     ` Matthew Wilcox
2009-06-27 18:40       ` Jaswinder Singh Rajput
2009-06-28 13:52         ` James Bottomley
2009-06-28 14:09           ` Boaz Harrosh
2009-07-02 14:41     ` Jaswinder Singh Rajput
2009-06-28  7:56 ` Boaz Harrosh
2009-06-28 14:32   ` James Smart
2009-06-28 14:44     ` James Bottomley
2009-06-28 16:00     ` Boaz Harrosh [this message]

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=4A4793A6.8080802@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=James.Smart@Emulex.Com \
    --cc=akpm@linux-foundation.org \
    --cc=bhalevy@panasas.com \
    --cc=hch@infradead.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=rdunlap@xenotime.net \
    --cc=sam@ravnborg.org \
    --cc=scst-devel@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.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