[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <216e8509-e7e8-5a5c-918c-a1a6e0e5285d@free.fr>
Date: Fri, 21 Apr 2017 10:30:11 +0200
From: Mason <slash.tmp@...e.fr>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Russell King <rmk@...linux.org.uk>,
linux-next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
arm-soc <arm@...nel.org>, Emilio Lopez <emilio@...pez.com.ar>,
dmaengine@...r.kernel.org, Vinod Koul <vinod.koul@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>
Subject: Re: linux-next: build failure after merge of the arm tree
On 21/04/2017 10:12, Stephen Rothwell wrote:
> Mason wrote:
>
>> Anyway, the fix is trivial.
>>
>> The "pchans_used" field is an unsigned long array.
>> for_each_clear_bit_from() expects an unsigned long pointer,
>> not an array address.
>>
>> I'll send a patch to the drivers/dma maintainers.
>
> The fix really needs to go into the arm tree (as well?) since that is
> the tree that has the patch that causes the build to break (even if the
> actual bug was preexisting).
Hello Stephen,
Since it's a trivial patch, and since Vinod is on vacation
until Monday, I suppose Russell could push the patch through
his own tree? (Maybe after an ACK from a sunxi maintainer.)
I am currently building an allyesconfig next-20170420 kernel.
Considering the speed of this system, this will take a while.
Regards.
Powered by blists - more mailing lists