[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170421234315.GO17774@n2100.armlinux.org.uk>
Date: Sat, 22 Apr 2017 00:43:16 +0100
From: Russell King - ARM Linux <linux@...linux.org.uk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Mason <slash.tmp@...e.fr>, 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 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.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
Powered by blists - more mailing lists