From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-scsi@vger.kernel.org
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [GIT PATCH] SCSI updates for 2.6.20
Date: Mon, 12 Feb 2007 16:21:18 +0100 [thread overview]
Message-ID: <200702121621.31232.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <1171291120.3690.0.camel@mulgrave.il.steeleye.com>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
James Bottomley wrote:
> On Mon, 2007-02-12 at 11:29 +0100, Rolf Eike Beer wrote:
> > Am Sonntag, 11. Februar 2007 schrieb James Bottomley:
> > > This is the accumulated SCSI tree for 2.6.20. It is available at
> > >
> > > master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
> >
> > You once again have not included this two patches Andrew sent you on
> > 20070602:
> >
> > [patch 08/33] remove extra newline from info message
>
> This one's waiting on Hannes to ack, since he's working in that driver
Ah, thanks. (Added Hannes to CC).
> > [patch 09/33] Fix scsi/scsi_transport.h compile error
>
> I did look at this one, but I can't find a configuration that will
> induce a compile error like the header says. It's pending further
> investigation.
Just try to compile a file that only includes this header. I don't know if
there is an existing (in-kernel) configuration where this can go wrong, I
found it when hacking a replacement for cpqfcTS. Nevertheless this is still a
bug, relying on a specific include order is just wrong.
Greetings,
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-02-12 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 3:57 [GIT PATCH] SCSI updates for 2.6.20 James Bottomley
2007-02-12 10:29 ` Rolf Eike Beer
2007-02-12 14:38 ` James Bottomley
2007-02-12 15:21 ` Rolf Eike Beer [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=200702121621.31232.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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.