dmaengine new location Re: linux-next: dropping trees

dmaengine new location Re: linux-next: dropping trees

[Dan Williams]

On Thu, Jan 19, 2012 at 4:40 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> The trees listed below were all hosted on git.kernel.org until the
> breakin.  These have not been restored and I have not been given an
> alternate location for them, so I will drop them all on Monday unless I
> hear from their maintainers (all cc'd).  On the other hand, if your tree
> is no longer needed, it would be good to know that as well.
>
[..]
> async_tx        git://git.kernel.org/pub/scm/linux/kernel/git/djbw/async_tx.git#next

Please add:

   git://git.kernel.org/pub/scm/linux/kernel/git/djbw/dmaengine.git next

to -next to replace the old async_tx.git tree.  It should be included
in the merge order after Vinod's slave dma tree at:

   git://git.infradead.org/users/vkoul/slave-dma.git next

I still expect the majority of dmaengine traffic to go through
slave-dma.git, with dmaengine.git picking up the memory-to-memory
offload specific bits.  The name change of async_tx.git to
dmaengine.git relates to the reworks needed to async_tx api which
needs replacement to fix dma mapping api violations.

Right now it only contains one patch:

commit d07a74a546981a09ba490936645fbf0d1340b96c
Author: Dr. David Alan Gilbert <linux@treblig.org>
Date:   Thu Aug 25 16:13:55 2011 -0700

    dmaengine: fix missing 'cnt' in ?: in dmatest

    Hi,
      On the latest tree my compiler has started giving the warning:

    drivers/dma/dmatest.c:575:28: warning: the omitted middle operand
in ?: will always be ?true?, suggest explicit middle op

    The following patch fixes the missing middle clause with the same
    fix that Nicolas Ferre used in the similar clauses.
    (There seems to have been a race between him fixing that and
    the extra clause going in a little later).

    I don't actually know the dmatest code/structures, nor do I own
    any hardware to test it on (assuming it needs a DMA engine);
     but this patch builds, the existing code is almost certainly
    wrong and the fix is the same as the corresponding lines above it.

    (WTH is x=y?:z legal C anyway?)

    Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reported-by: Paul Gortmaker <paul.gortmaker@windriver.com>
    Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
    Signed-off-by: Dan Williams <dan.j.williams@intel.com>


--
Dan

Re: dmaengine new location Re: linux-next: dropping trees

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]

Hi Dan,

On Tue, 24 Jan 2012 00:40:55 -0800 Dan Williams <dan.j.williams@intel.com> wrote:
>
> Please add:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/djbw/dmaengine.git next
> 
> to -next to replace the old async_tx.git tree.  It should be included
> in the merge order after Vinod's slave dma tree at:
> 
>    git://git.infradead.org/users/vkoul/slave-dma.git next

I have added that from today.

Just for completeness:

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]