From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] intermediate SCSI updates
Date: Mon, 13 Oct 2008 18:22:05 -0400 [thread overview]
Message-ID: <yq163nwcf02.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0810131416410.3288@nehalem.linux-foundation.org> (Linus Torvalds's message of "Mon\, 13 Oct 2008 14\:22\:13 -0700 \(PDT\)")
>>>>> "Linus" == Linus Torvalds <torvalds@linux-foundation.org> writes:
Linus> What I'm upset about is that this has apparently gotten not
Linus> even some trivial testing of the _default_ build. I'm not
Linus> talking about any odd config options here. I'm literally
Linus> talking about the only _sane_ config option case.
This one initially slipped through my testing, sorry about that. I
always compile with the integrity both on and off in my devel tree but
I messed up while rebasing the patches against James' tree. These
mutually dependent block and SCSI merges are always tricky to deal
with.
However, I wonder why the obvious build fix wasn't merged? Mike
Anderson sent out a patch for this right after my patch appeared in
the SCSI tree...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2008-10-13 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 14:45 [GIT PATCH] intermediate SCSI updates James Bottomley
2008-10-13 17:22 ` Linus Torvalds
2008-10-13 19:20 ` James Bottomley
2008-10-13 21:22 ` Linus Torvalds
2008-10-13 22:02 ` Paul Mackerras
2008-10-13 22:22 ` Martin K. Petersen [this message]
2008-10-13 23:44 ` Stephen Rothwell
2008-10-14 12:49 ` James Bottomley
2008-10-17 15:11 ` [GIT PATCH] intermediate SCSI updates (v2) James Bottomley
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=yq163nwcf02.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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