From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ub.c badness in current bk
Date: Mon, 20 Sep 2004 13:37:27 +1000 [thread overview]
Message-ID: <1095651446.31131.48.camel@gaston> (raw)
In-Reply-To: <20040919202126.1073925b@lembas.zaitcev.lan>
On Mon, 2004-09-20 at 13:21, Pete Zaitcev wrote:
> How about this deal. I'll add a clearly marked workaround like the
> appended patch, and then ask you to try again when a proper spin-up gets
> implemented?
Ok, I'll give it a try, but you don't need to call it "benh's key" :) I
think everybody at kernel summit got one of those no ? :)
Ben.
> Note that the patch is against -mm where the REQUEST SENSE is set correctly.
> I strongly suggest you to use ub from -mm. Linus' tree is behind.
>
> Also, I might have screwed something along the way, so if it fails, please
> send me dmesg and the contents of /sys/..../diag.
I will later today or tomorrow, thanks !
Ben.
next prev parent reply other threads:[~2004-09-20 3:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1095300780.10032.linux-kernel2news@redhat.com>
2004-09-16 6:17 ` [BUG] ub.c badness in current bk Pete Zaitcev
2004-09-17 7:29 ` Pete Zaitcev
2004-09-17 9:46 ` Benjamin Herrenschmidt
2004-09-17 16:04 ` Pete Zaitcev
2004-09-18 0:08 ` Benjamin Herrenschmidt
2004-09-18 0:12 ` Benjamin Herrenschmidt
2004-09-18 1:04 ` Benjamin Herrenschmidt
2004-09-18 2:08 ` Benjamin Herrenschmidt
2004-09-20 3:21 ` Pete Zaitcev
2004-09-20 3:37 ` Benjamin Herrenschmidt [this message]
2004-09-22 1:44 ` Pete Zaitcev
2004-09-16 2:06 Benjamin Herrenschmidt
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=1095651446.31131.48.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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