From: Borislav Petkov <bp@alien8.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
mroos@linux.ee, JBottomley@parallels.com
Subject: Re: [PATCH v2 0/4] fix / cleanup async scsi scanning
Date: Thu, 31 May 2012 15:37:21 +0200 [thread overview]
Message-ID: <20120531133720.GA21281@x1.osrc.amd.com> (raw)
In-Reply-To: <CABE8wwsw98KZS0W1sJghzrei0mSGLiMoh+7Wn5xOzdM54qiYqA@mail.gmail.com>
On Wed, May 30, 2012 at 11:29:23AM -0700, Dan Williams wrote:
> They're ready for a run, but are likely 3.6 material. For 3.5 I think
> James is going with the smaller fix posted here:
>
> http://marc.info/?l=linux-scsi&m=133796775807498&w=2
Yep,
both the smaller fix and the 4-patch set cure the box here, thanks.
Tested-by: Borislav Petkov <bp@alien8.de>
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-05-31 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 18:21 [PATCH v2 0/4] fix / cleanup async scsi scanning Dan Williams
2012-05-30 18:21 ` [PATCH v2 1/4] async: introduce 'async_domain' type Dan Williams
2012-05-30 18:21 ` [PATCH v2 2/4] async: make async_synchronize_full() flush all work regardless of domain Dan Williams
2012-05-30 18:21 ` [PATCH v2 3/4] scsi: queue async scan work to an async_schedule domain Dan Williams
2012-05-30 18:21 ` [PATCH v2 4/4] scsi: cleanup usages of scsi_complete_async_scans Dan Williams
2012-05-30 21:34 ` Rafael J. Wysocki
2012-05-30 21:37 ` Rafael J. Wysocki
2012-05-30 21:41 ` Rafael J. Wysocki
2012-05-30 21:49 ` Dan Williams
2012-05-30 21:49 ` Dan Williams
2012-05-30 18:22 ` [PATCH v2 0/4] fix / cleanup async scsi scanning Borislav Petkov
2012-05-30 18:29 ` Dan Williams
2012-05-30 22:33 ` walt
2012-05-31 13:37 ` Borislav Petkov [this message]
2012-05-31 9:05 ` mroos
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=20120531133720.GA21281@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=JBottomley@parallels.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mroos@linux.ee \
/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.