All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"neilb@suse.de" <neilb@suse.de>, "hpa@zytor.com" <hpa@zytor.com>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"Sosnowski, Maciej" <maciej.sosnowski@intel.com>
Subject: Re: What's in async_tx.git/next for 2.6.32?
Date: Sun, 13 Sep 2009 10:16:34 -0700	[thread overview]
Message-ID: <4AAD28F2.3040606@intel.com> (raw)
In-Reply-To: <20090914.013052.84972601.anemo@mba.ocn.ne.jp>

Atsushi Nemoto wrote:
> On Sat, 05 Sep 2009 12:22:43 -0700, Dan Williams <dan.j.williams@intel.com> wrote:
>> Provided Neil and Peter provide their acks for the raid6 acceleration 
>> work, here is what is pending in async_tx.git/next for 2.6.32:
> ...
>>     git://git.kernel.org/pub/scm/linux/kernel/git/djbw/async_tx.git next
>>
>> Dan Williams (67):
> ...
>>        dw_dmac: implement a private tx_list
>>        fsldma: implement a private tx_list
>>        iop-adma: implement a private tx_list
>>        ioat: implement a private tx_list
>>        mv_xor: implement a private tx_list
>>        at_hdmac: implement a private tx_list
>>        dmaengine: kill tx_list
> 
> Could you implement a private tx_list for txx9dmac too?

I noticed that too when I merged with -next.  I forgot to send this [1] out.

Thanks,
Dan

[1]: 
http://git.kernel.org/?p=linux/kernel/git/djbw/async_tx.git;a=commitdiff;h=1979b186b80449ac6574d97c254b694c8a99b703

  reply	other threads:[~2009-09-13 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 19:22 What's in async_tx.git/next for 2.6.32? Dan Williams
2009-09-13 16:30 ` Atsushi Nemoto
2009-09-13 17:16   ` Dan Williams [this message]
2009-09-15 16:12     ` Atsushi Nemoto

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=4AAD28F2.3040606@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=maciej.sosnowski@intel.com \
    --cc=neilb@suse.de \
    /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.