From: Luben Tuikov <ltuikov@yahoo.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Richard Senior <richard@r-senior.demon.co.uk>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] sd: Fix regression in sd_read_cache_type
Date: Wed, 23 Mar 2011 08:54:32 -0700 (PDT) [thread overview]
Message-ID: <358235.77053.qm@web31810.mail.mud.yahoo.com> (raw)
In-Reply-To: <1300893408.15899.17.camel@mulgrave.site>
--- On Wed, 3/23/11, James Bottomley <James.Bottomley@suse.de> wrote:
>
> I put the original patch in on the understanding from both
> of you that
> the chances of finding a USB device which crashed with the
> change was
> very small.
Bottomley, obviously there are no guarantees in life. This is what bug fixes and code development is all about. It's all about making things better for for a wider range of NEW devices.
> Given that several have been found and we're on the eve of
> the merge window closure,
It wouldn't have mattered it if was found two weeks ago or in a month.
> I'll just revert the original,
Obviously you don't have to do that if you applied Alan patch.
> and you two can work on getting a bullet proof version for the next
> merge window.
Here is what happened: I submitted a patch and it was generally liked. To
refresh your memory here is the thread: http://marc.info/?t=129044508400003&r=1&w=2. The patch was applied. Then an odd device was
found, as reported by Alan, who fixed it, and submitted a patch. He agreed
that his patch works on top of mine to fix the problem. It was verified to
fix the problem by Richard. Then I agreed with Alan that his patch works
on top of mine to fix the problem by acking it as you can see in this
thread. So Alan and I have both agreed that this is, at the moment, a
"bullet-proof" version for this and any other merge window.
Having said that, you should be aware that no patch is "bullet-proof",
neither is the SCSI Layer, nor is the Linux kernel. That is, as technology
goes forward.
If you prefer to revert the original patch, I can resubmit the original
patch with Alan's patch on top of it (as it is a fix for the original,
larger, topic patch), and then you can apply that.
Let me know what would work for you Bottomley.
Luben
next prev parent reply other threads:[~2011-03-23 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 21:29 [PATCH] sd: Fix regression in sd_read_cache_type Alan Stern
2011-03-23 14:06 ` Luben Tuikov
2011-03-23 15:16 ` James Bottomley
2011-03-23 15:54 ` Luben Tuikov [this message]
2011-03-23 16:12 ` Alan Stern
2011-03-23 16:44 ` Luben Tuikov
2011-03-23 17:23 ` Alan Stern
2011-03-23 17:55 ` Luben Tuikov
2011-03-23 18:30 ` Alan Stern
2011-03-23 16:18 ` [PATCH ver. 2] " Alan Stern
2011-03-23 17:40 ` Luben Tuikov
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=358235.77053.qm@web31810.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=James.Bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=richard@r-senior.demon.co.uk \
--cc=stern@rowland.harvard.edu \
/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