From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: amba-pl08x and 'get_signal' namespace collision/build error
Date: Sun, 7 Jul 2013 19:04:53 +0530 [thread overview]
Message-ID: <20130707133453.GC16653@intel.com> (raw)
In-Reply-To: <20130707123240.GO24642@n2100.arm.linux.org.uk>
On Sun, Jul 07, 2013 at 01:32:40PM +0100, Russell King - ARM Linux wrote:
> On Fri, Jul 05, 2013 at 11:48:02AM +0530, Vinod Koul wrote:
> > On Wed, Jul 03, 2013 at 11:27:12AM -0700, Olof Johansson wrote:
> > > This has now hit the mainline kernel, and several defconfigs (nhk815,
> > > lpc32xx and the spear ones) are broken there.
> > >
> > > Vinod, when are you sending up your pull request with the fix? It'd be
> > > good to see it go in soon.
> > It should be on its way by the weekend
>
> It still isn't in the tree.
I sent this morning, depends on how soon can linus merge this
>
> Personally, I think that the fix should have come via my tree, because
> the breakage was caused my the changes in my tree - and for the last week
> or more I've not been able to build any of these ARM Ltd devel platforms
> because of this bug.
>
> It also means that I'm not able to build test a load of changes I'm
> currently working on against a recent kernel (or indeed any v3.10 kernel.)
> In other words, the lack of this patch being merged is stopping me from
> doing my job properly. (Consider from your perspective: if I were to
> break something you relied upon for a couple of weeks, how would you
> feel about it?)
>
> Please get this fix into mainline ASAP - even if you have to send it as a
> patch separately to Linus rather than putting it as part of your normal
> pull request.
Yes it could have gone thur your tree as well, or you could have merged my tree
to resolve your breakage
--
Thanks
~Vinod
next prev parent reply other threads:[~2013-07-07 13:34 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
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 [this message]
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=20130707133453.GC16653@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).