Re: linux-next: build failure after merge of the arm tree

From	Mason <slash.tmp@free.fr>
Newsgroups	linux.kernel
Subject	Re: linux-next: build failure after merge of the arm tree
Date	2017-06-14 21:30 +0200
Message-ID	<tSm9j-MK-1@gated-at.bofh.it> (permalink)
References	<tyt3H-6m1-1@gated-at.bofh.it> <tyBDX-39t-11@gated-at.bofh.it> <tyBXj-3uU-1@gated-at.bofh.it> <tyQtk-3Gv-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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@free.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.

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: linux-next: build failure after merge of the arm tree Mason <slash.tmp@free.fr> - 2017-06-14 21:30 +0200

csiph-web