From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: mroos@linux.ee, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
James Bottomley <JBottomley@parallels.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/4] async: introduce 'async_domain' type
Date: Sun, 27 May 2012 23:34:49 +0100 [thread overview]
Message-ID: <20120527223449.GD25019@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120525075027.21933.75815.stgit@dwillia2-linux.jf.intel.com>
On Fri, May 25, 2012 at 12:50:27AM -0700, Dan Williams wrote:
> This is in preparation for teaching async_synchronize_full() to sync all
> pending async work, and not just on the async_running domain. This
> conversion is functionally equivalent, just embedding the existing list
> in a new async_domain type.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2012-05-27 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:50 [RFT PATCH 0/4] fix / cleanup async scsi scanning Dan Williams
2012-05-25 7:50 ` [PATCH 1/4] async: introduce 'async_domain' type Dan Williams
2012-05-25 7:51 ` James Bottomley
2012-05-25 8:18 ` Dan Williams
2012-05-25 8:18 ` Dan Williams
2012-05-25 8:48 ` James Bottomley
2012-05-25 19:23 ` Rafael J. Wysocki
2012-05-25 13:31 ` Arjan van de Ven
2012-05-25 13:40 ` mroos
2012-05-25 15:05 ` Dan Williams
2012-05-27 22:34 ` Mark Brown [this message]
2012-05-25 7:50 ` [PATCH 2/4] async: make async_synchronize_full() flush all work regardless of domain Dan Williams
2012-05-25 7:50 ` [PATCH 3/4] scsi: queue async scan work to an async_schedule domain Dan Williams
2012-05-25 7:50 ` [PATCH 4/4] scsi: cleanup usages of scsi_complete_async_scans Dan Williams
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=20120527223449.GD25019@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=JBottomley@parallels.com \
--cc=arjan@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lrg@ti.com \
--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.