From: Linus Walleij <linus.walleij@linaro.org>
To: Jonathan Austin <jonathan.austin@arm.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vinod Koul <vinod.koul@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Steve Capper <Steve.Capper@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: amba-pl08x and 'get_signal' namespace collision/build error
Date: Tue, 25 Jun 2013 15:49:57 +0200 [thread overview]
Message-ID: <CACRpkdb-Fhz3pjWm3xVguitv6h0-+ywyo3HFDVgqgHcZ-MjKKA@mail.gmail.com> (raw)
In-Reply-To: <51C97F40.5030101@arm.com>
On Tue, Jun 25, 2013 at 1:30 PM, Jonathan Austin
<jonathan.austin@arm.com> wrote:
> There's a patch making its way to mainline via Russell's tree
> (8d96250700: ARM: mm: Transparent huge page support for LPAE systems)
> that breaks the build of the amba-pl08x driver (drivers/dma/amba-pl08x.c)
> because the 'get_signal' macro from include/linux/signal.h is now in the
> driver's scope and it clobbers a (previously) valid function call.
This is already fixed by Mark Brown in the DMA tree.
Commit subject:
"dmaengine: PL08x: Avoid collisions with get_signal() macro"
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-06-25 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 11:30 amba-pl08x and 'get_signal' namespace collision/build error Jonathan Austin
2013-06-25 13:49 ` Linus Walleij [this message]
2013-06-25 18:45 ` Russell King - ARM Linux
2013-06-26 4:48 ` Vinod Koul
2013-06-26 8:19 ` Russell King - ARM Linux
2013-06-26 10:39 ` Vinod Koul
2013-06-26 12:00 ` Mark Brown
2013-06-27 9:46 ` Russell King - ARM Linux
2013-07-03 18:27 ` Olof Johansson
2013-07-05 6:18 ` Vinod Koul
2013-07-07 12:32 ` Russell King - ARM Linux
2013-07-07 13:34 ` Vinod Koul
2013-07-08 2:04 ` Vinod Koul
2013-06-26 8:40 ` Steve Capper
2013-06-26 9:13 ` Steve Capper
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=CACRpkdb-Fhz3pjWm3xVguitv6h0-+ywyo3HFDVgqgHcZ-MjKKA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Steve.Capper@arm.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jonathan.austin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@arm.com \
/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).