From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] tgt: Use scsi_init_io instead of scsi_alloc_sgtable
Date: Sun, 06 Jan 2008 11:18:43 -0600 [thread overview]
Message-ID: <1199639923.5205.61.camel@localhost.localdomain> (raw)
In-Reply-To: <47810B26.1090709@panasas.com>
On Sun, 2008-01-06 at 19:08 +0200, Boaz Harrosh wrote:
> On Sat, Jan 05 2008 at 1:02 +0200, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> > On Thu, 2007-12-13 at 13:44 +0200, Boaz Harrosh wrote:
> >> - If we export scsi_init_io()/scsi_release_buffers() instead of
> >> scsi_{alloc,free}_sgtable() from scsi_lib than tgt code is
> >> much more insulated from scsi_lib changes. As a bonus it will
> >> also gain bidi capability when it comes.
> >>
> >> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
> >> Acked-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> >
> > I'm afraid the reversion of ->done removal broke the application of this
> > yet again ... could you respin.
> >
> > Thanks,
> >
> > James
> >
> It looks like the revert is to be reverted ;)
> I have rebased, but should I wait a while to
> see if they're needed?
Yes, let's just wait a while to see what the outcome is ...
James
next prev parent reply other threads:[~2008-01-06 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 11:37 [0/3 ver2] Last 3 patches for bidi support Boaz Harrosh
2007-12-13 11:44 ` [PATCH] tgt: Use scsi_init_io instead of scsi_alloc_sgtable Boaz Harrosh
2008-01-04 23:02 ` James Bottomley
2008-01-06 17:08 ` Boaz Harrosh
2008-01-06 17:18 ` James Bottomley [this message]
2007-12-13 11:47 ` [PATCH] scsi: scsi_data_buffer Boaz Harrosh
2007-12-13 11:50 ` [PATCH] scsi: bidi support Boaz Harrosh
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=1199639923.5205.61.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.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