From: Mason <slash.tmp@free.fr>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <rmk@armlinux.org.uk>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
arm-soc <arm@kernel.org>, Emilio Lopez <emilio@elopez.com.ar>,
dmaengine@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: linux-next: build failure after merge of the arm tree
Date: Fri, 21 Apr 2017 10:30:11 +0200 [thread overview]
Message-ID: <216e8509-e7e8-5a5c-918c-a1a6e0e5285d@free.fr> (raw)
In-Reply-To: <20170421181230.05dcf937@canb.auug.org.au>
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.
next prev parent reply other threads:[~2017-04-21 8:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 22:40 linux-next: build failure after merge of the arm tree Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 8:06 ` [PATCH] dmaengine: sun4i: fix invalid argument Mason
2017-04-21 8:24 ` Maxime Ripard
2017-04-21 8:43 ` [PATCH v2] " Mason
2017-04-21 14:40 ` Maxime Ripard
2017-04-21 8:12 ` linux-next: build failure after merge of the arm tree Stephen Rothwell
2017-04-21 8:30 ` Mason [this message]
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul
2017-04-26 22:34 ` [PATCH v2] arm: bitops: Align prototypes to generic API Mason
2017-06-14 19:23 ` linux-next: build failure after merge of the arm tree Mason
2017-04-21 11:27 ` Mason
-- strict thread matches above, loose matches on Subject: below --
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2021-10-25 23:25 Stephen Rothwell
2020-01-19 21:24 Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=216e8509-e7e8-5a5c-918c-a1a6e0e5285d@free.fr \
--to=slash.tmp@free.fr \
--cc=arm@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=rmk@armlinux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=vinod.koul@intel.com \
--cc=wens@csie.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).