LKML Archive on
help / color / mirror / Atom feed
From: "Dan Williams" <>
To: "Stephen Rothwell" <>,
	"Andrew Morton" <>
Cc:, LKML <>
Subject: Re: linux-next: Tree for March 4
Date: Tue, 4 Mar 2008 10:54:41 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Mar 4, 2008 at 4:39 AM, Stephen Rothwell <> wrote:
>  We are up to 40 trees, more are welcome (even if they are currently
>  empty).  The influx of new trees has been underwhelming.  Thanks to those
>  who have contributed, and to those who haven't, please do.

Hello Stephen, Andrew,

I have recently moved the async_tx git tree to

For linux-next please add: next

For -mm please replace the 'git-md-accel' url with the following, it
should also be renamed to 'git-async-tx' as anything that impacts MD
will go through Neil. upstream

Currently both trees contain the following:
Dan Williams (7):
      fsldma: do not cleanup descriptors in hardirq context
      dmaengine: fix sparse warning
      ioat: fix 'ack' handling, driver must ensure that 'ack' is zero
      async_tx: checkpatch says s/__FUNCTION__/__func__/g
      async_tx: fix multiple dependency submission
      async_tx: kill ->device_dependency_added
      iop-adma: remove the workaround for missed interrupts on iop3xx

Zhang Wei (1):
      dmaengine: add driver for Freescale MPC85xx DMA controller


  reply	other threads:[~2008-03-04 17:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 11:39 Stephen Rothwell
2008-03-04 17:54 ` Dan Williams [this message]
2008-03-04 23:25   ` Stephen Rothwell
2008-03-04 21:01 ` Stefan Richter
2008-03-05  7:41   ` Sam Ravnborg
2008-03-05  7:57   ` Stephen Rothwell
2009-03-04  7:06 Stephen Rothwell
2009-03-04 21:57 ` Geert Uytterhoeven
2009-03-04 22:44   ` Stephen Rothwell
2009-03-05  9:11     ` Stephen Rothwell
2009-03-05 10:27       ` Geert Uytterhoeven
2010-03-04  6:26 Stephen Rothwell
2011-03-04  7:00 Stephen Rothwell
2011-03-06 22:52 ` Mariusz Kozlowski
2011-03-07 11:46   ` Mark Brown

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: linux-next: Tree for March 4' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).