From: Boaz Harrosh <bharrosh@panasas.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
Oliver Neukum <oliver@neukum.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [BUG] 2.6.24-git usb reset problems
Date: Tue, 29 Jan 2008 22:26:48 +0200 [thread overview]
Message-ID: <479F8C08.2060207@panasas.com> (raw)
In-Reply-To: <20080129201328.GZ15220@kernel.dk>
On Tue, Jan 29 2008 at 22:13 +0200, Jens Axboe <jens.axboe@oracle.com> wrote:
> On Tue, Jan 29 2008, Boaz Harrosh wrote:
>>> Ok this is not in Linus tree is it? Hence I did not have that failure.
>>>
>>> Boaz
>>>
>>>
>> actually James bidi tree has a fix for this in the scsi_data_buffer patch.
>>
>> what you sent is not enough there are other places. look at this patch I
>> sent to the list.
>>
>> http://www.spinics.net/lists/linux-scsi/msg21938.html
>
> Hard to compare, since its on different bases.
Yes in this patchset I have taken your sg branch at the time, and
rebased it ontop of scsi_data_buffer patch. Because I felt that
it is more natural for this patch to come after the scsi total
cleanup that is scsi_data_buffer. Then the extraction to sg_table
is simple and trivial.
What I meant to point out with this patch is that all the exact same
places that are touched there should be fixed when moving to sg_table.
Look at it. It is a revised version of your patch.
>
>> Could we take the 2 SG patches and submit them through the scsi
>> bidi tree? It is much more natural to have them in one tree as one
>> patchset then try coordinate with git-merge. Actually if you look at it,
>> the biggest change is to SCSI. So I think it is more natural this way
>
> What 2 sg patches do you mean?
>
I mean the patches that where in sg branch of the linux-block tree, But
I see that it is now to late, and that they are in Linus already
James the most simple is to submit the scsi_data_buff patch that fixes
all these places. If not do you want that I send in fixes?
Boaz
next prev parent reply other threads:[~2008-01-29 20:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 20:49 Jens Axboe
2008-01-28 21:21 ` Greg KH
2008-01-29 7:48 ` Jens Axboe
2008-01-29 12:15 ` Boaz Harrosh
2008-01-29 13:54 ` Jens Axboe
2008-01-29 14:06 ` Boaz Harrosh
2008-01-29 14:11 ` Jens Axboe
2008-01-29 14:14 ` Boaz Harrosh
2008-01-29 14:31 ` Oliver Neukum
2008-01-29 14:31 ` Jens Axboe
2008-01-29 18:39 ` Jens Axboe
2008-01-29 19:09 ` Boaz Harrosh
2008-01-29 19:10 ` Matthew Dharm
2008-01-29 19:15 ` Jens Axboe
2008-01-29 19:26 ` Jens Axboe
2008-01-29 19:37 ` Matthew Dharm
2008-01-29 19:33 ` James Bottomley
2008-01-29 19:35 ` Jens Axboe
2008-01-29 19:45 ` Jens Axboe
2008-01-29 19:58 ` Boaz Harrosh
2008-01-29 20:03 ` Jens Axboe
2008-01-29 20:04 ` James Bottomley
2008-01-29 20:06 ` Jens Axboe
2008-01-29 20:24 ` James Bottomley
2008-01-29 20:53 ` Boaz Harrosh
2008-01-29 20:09 ` Boaz Harrosh
2008-01-29 20:13 ` Jens Axboe
2008-01-29 20:26 ` Boaz Harrosh [this message]
2008-01-30 10:27 ` Geert Uytterhoeven
2008-01-30 10:38 ` Jens Axboe
2008-01-30 14:38 ` James Bottomley
2008-01-30 18:06 ` Jens Axboe
2008-01-30 19:07 ` Jens Axboe
2008-01-29 15:50 ` Boaz Harrosh
2008-01-29 17:42 ` Oliver Neukum
2008-01-29 14:13 ` Boaz Harrosh
2008-01-29 15:00 ` Matthew Dharm
2008-01-29 15:36 ` Alan Stern
2008-01-29 15:54 ` Boaz Harrosh
2008-01-29 16:34 ` James Bottomley
2008-01-29 18:27 ` Boaz Harrosh
2008-01-29 18:48 ` James Bottomley
2008-01-29 18:58 ` Boaz Harrosh
2008-01-29 19:17 ` James Bottomley
2008-01-29 19:28 ` 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=479F8C08.2060207@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=greg@kroah.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=oliver@neukum.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
Powered by JetHome