From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>, Greg KH <greg@kroah.com>,
linux-next@vger.kernel.org, scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] libsas: Check that the firmware loader is present in sas_request_addr
Date: Thu, 06 Mar 2008 16:16:21 -0600 [thread overview]
Message-ID: <1204841781.3062.69.camel@localhost.localdomain> (raw)
In-Reply-To: <20080306140437.8a193423.randy.dunlap@oracle.com>
On Thu, 2008-03-06 at 14:04 -0800, Randy Dunlap wrote:
> On Thu, 06 Mar 2008 15:17:13 -0600 James Bottomley wrote:
>
> > We could do it that way ... I suspect what Greg was asking for was more
> > like this:
> >
> > James
>
> Builds cleanly for CONFIG_FW_LOADER=n.
> I'm having trouble setting CONFIG_FW_LOADER=m for test building it.
Ironically, I can, and have, tested that config ... I just couldn't
build with CONFIG_FW_LOADER=n.
I think we've covered all the test cases between us.
> Anyway,
> Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
James
next prev parent reply other threads:[~2008-03-06 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 17:09 next-2008-0306 scsi/libsas build failure Randy Dunlap
2008-03-06 18:16 ` Greg KH
2008-03-06 18:22 ` Randy Dunlap
2008-03-06 21:01 ` Darrick J. Wong
2008-03-06 21:02 ` [PATCH] libsas: Check that the firmware loader is present in sas_request_addr Darrick J. Wong
2008-03-06 21:17 ` James Bottomley
2008-03-06 21:20 ` Randy Dunlap
2008-03-06 22:04 ` Randy Dunlap
2008-03-06 22:16 ` James Bottomley [this message]
2008-03-07 4:54 ` Greg KH
2008-03-07 14:57 ` [PATCH] firmware: provide stubs for the FW_LOADER=n case James Bottomley
2008-03-07 17:08 ` patch firmware-provide-stubs-for-the-fw_loader-n-case.patch added to gregkh-2.6 tree gregkh
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=1204841781.3062.69.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=djwong@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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