From: Christoph Hellwig <hch@infradead.org>
To: Janusz Dziemidowicz <rraptorr@nails.eu.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 79901] [BISECTED]Extremely slow boot on Promise VTrak E610f due to sd_mod RSOC usage
Date: Tue, 29 Jul 2014 14:56:49 -0700 [thread overview]
Message-ID: <20140729215649.GA10749@infradead.org> (raw)
In-Reply-To: <bug-79901-11613-ViyKhyhm4Z@https.bugzilla.kernel.org/>
On Tue, Jul 29, 2014 at 07:07:51PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=79901
>
> --- Comment #3 from Janusz Dziemidowicz <rraptorr@nails.eu.org> ---
> I've read that document before creating the patch. Now, I've read it again. I
> must say I'm at a loss. In the patch attached to this bug entry I've already
> included Signed-off-by line.
> Can anyone point precisely what is wrong here?
Everything is fine and I already applied your patch. Thanks a lot for
debugging the issue and coming up with the patch!
next prev parent reply other threads:[~2014-07-29 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 13:23 [Bug 79901] New: Extremely slow boot on Promise VTrak E610f due to sd_mod RSOC usage bugzilla-daemon
2014-07-10 13:54 ` Christoph Hellwig
2014-07-10 14:10 ` Janusz Dziemidowicz
2014-07-24 14:07 ` [Bug 79901] " bugzilla-daemon
2014-07-24 15:28 ` Christoph Hellwig
2014-07-29 12:53 ` [PATCH] Do not issue SCSI RSOC command to Promise Vtrak E610f " Christoph Hellwig
2014-07-29 12:57 ` Hannes Reinecke
2014-07-29 13:00 ` Martin K. Petersen
2014-07-29 13:14 ` Hannes Reinecke
2014-07-29 16:05 ` [Bug 79901] [BISECTED]Extremely slow boot on Promise VTrak E610f due to " bugzilla-daemon
2014-07-29 19:07 ` bugzilla-daemon
2014-07-29 21:56 ` Christoph Hellwig [this message]
2014-07-29 20:26 ` bugzilla-daemon
2014-07-29 20:26 ` bugzilla-daemon
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=20140729215649.GA10749@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rraptorr@nails.eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.