[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b5189473-bfdd-4e4e-711f-0f48ac9da5c8@free.fr>
Date: Wed, 14 Jun 2017 21:23:07 +0200
From: Mason <slash.tmp@...e.fr>
To: Russell King - ARM Linux <linux@...linux.org.uk>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: 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.lopez@...labora.co.uk>,
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 22/04/2017 01:43, Russell King - ARM Linux wrote:
> On Fri, Apr 21, 2017 at 06:12:30PM +1000, Stephen Rothwell wrote:
>> Hi Mason,
>>
>> On Fri, 21 Apr 2017 09:58:58 +0200 Mason <slash.tmp@...e.fr> 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).
>
> Or I drop the offending patch (done) and we get the DMA subsystem fixed
> first. Given how long it's been this way, I doubt there's any hurry to
> get this change in for the next merge window.
Hello Russell,
Is it safe to apply the patch now?
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8679/1
Regards.
Powered by blists - more mailing lists