From: James Bottomley <James.Bottomley@SteelEye.com>
To: Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>
Cc: fujita.tomonori@lab.ntt.co.jp, linuxppc-dev@ozlabs.org,
Gala Kumar-B11780 <kumar.gala@freescale.com>,
paulus@samba.org, linux-scsi@vger.kernel.org
Subject: Re: CONFIG_BLK_DEV_BSG=n
Date: Fri, 14 Sep 2007 15:00:08 -0500 [thread overview]
Message-ID: <1189800008.3343.21.camel@localhost.localdomain> (raw)
In-Reply-To: <598D5675D34BE349929AF5EDE9B03E27015558EA@az33exm24.fsl.freescale.net>
On Fri, 2007-09-14 at 12:50 -0700, Medve Emilian-EMMEDVE1 wrote:
> Which solution would you be more comfortable with?
The one which is currently in -mm is this one:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=49892223f7d3a2333ef9e6cbdd526676e1fc517a
James
next prev parent reply other threads:[~2007-09-14 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 19:50 CONFIG_BLK_DEV_BSG=n Medve Emilian-EMMEDVE1
2007-09-14 20:00 ` James Bottomley [this message]
2007-09-17 14:46 ` CONFIG_BLK_DEV_BSG=n David Howells
2007-09-19 12:53 ` CONFIG_BLK_DEV_BSG=n Jens Axboe
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=1189800008.3343.21.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=Emilian.Medve@freescale.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kumar.gala@freescale.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).