From: Russell King <rmk@arm.linux.org.uk>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Sundar R IYER <sundar.iyer@stericsson.com>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: FW: next build fails
Date: Fri, 17 Sep 2010 11:35:20 +0100 [thread overview]
Message-ID: <20100917103520.GA30330@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1284674935.2411.54.camel@c-dwalke-linux.qualcomm.com>
On Thu, Sep 16, 2010 at 03:08:55PM -0700, Daniel Walker wrote:
> On Fri, 2010-09-17 at 08:04 +1000, Stephen Rothwell wrote:
> > Hi Daniel,
> >
> > On Thu, 16 Sep 2010 14:58:57 -0700 Daniel Walker <dwalker@fifo99.com> wrote:
> > >
> > > Yeah, exactly .. This is what I did to update my patch .. Do you want to
> > > include this, or should I update my version and my tree.. Ultimately my
> > > version has to go into Russell's tree..
> >
> > Well, you can't really update that in your tree until after your tree is
> > merged with Russell's, right (since ALT_UP etc are not defined in your
> > tree)? In that case, I need to do the fix when I merge your tree into
> > linux-next (and so with Russell's tree).
>
> Right, I see what your saying .. Ok, thanks.
There is another way to handle this - we shouldn't be tinkering with
the aux control register on non-ARM cores (as we don't know what the
bits on such cores do) we could view this as a bug fix, and put it
into -rc.
I'd prefer to do that - so could you send the original patch you posted
to lakml to the patch system please?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2010-09-17 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <33A307AF30D7BF4F811B1568FE7A9B18043784FF99@EXDCVYMBSTM006.EQ1STM.local>
2010-09-16 6:44 ` FW: next build fails Stephen Rothwell
2010-09-16 17:00 ` Daniel Walker
2010-09-16 21:52 ` Stephen Rothwell
2010-09-16 21:58 ` Daniel Walker
2010-09-16 22:04 ` Stephen Rothwell
2010-09-16 22:08 ` Daniel Walker
2010-09-17 10:35 ` Russell King [this message]
2010-09-17 15:44 ` Daniel Walker
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=20100917103520.GA30330@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dwalker@fifo99.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sundar.iyer@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.