All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: consistent use of __u8 in scsi/scsi.h
Date: Thu, 30 Jul 2009 12:34:03 +0300	[thread overview]
Message-ID: <20090730093403.GA11381@redhat.com> (raw)
In-Reply-To: <4A7166A3.70509@panasas.com>

On Thu, Jul 30, 2009 at 12:23:47PM +0300, Boaz Harrosh wrote:
> >> I did a quick diff of the glibc provided scsi.h and kernel scsi.h.
> >> >From a quick look it seems that we have more in the kernel version
> >> than the glibc version - and no obvious conflicts.
> >>
> 
> exactly it is original Kernel headers from the time they where sampled
> last by glibc.

glibc also added
#include <features.h>
in some of them.
Donnu why.


  reply	other threads:[~2009-07-30  9:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 11:11 [PATCH] scsi: consistent use of __u8 in scsi/scsi.h Michael S. Tsirkin
2009-07-29 11:11 ` Michael S. Tsirkin
2009-07-29 13:56 ` James Bottomley
2009-07-29 14:09   ` Boaz Harrosh
2009-07-29 20:56     ` Michael S. Tsirkin
2009-07-30  9:05       ` Boaz Harrosh
2009-07-30  9:45         ` Michael S. Tsirkin
2009-07-30  9:36     ` Michael S. Tsirkin
2009-07-30 13:16       ` Boaz Harrosh
2009-07-29 16:28   ` Sam Ravnborg
2009-07-29 16:37     ` James Bottomley
2009-07-29 19:29       ` Sam Ravnborg
2009-07-30  9:23       ` Boaz Harrosh
2009-07-30  9:34         ` Michael S. Tsirkin [this message]
2009-07-30 10:40           ` Sam Ravnborg
2009-07-29 21:11   ` Michael S. Tsirkin
2009-08-16 13:42   ` Michael S. Tsirkin

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=20090730093403.GA11381@redhat.com \
    --to=mst@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sam@ravnborg.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.