From: Daniel Walker <dwalker@fifo99•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Sundar R IYER <sundar.iyer@stericsson•com>,
Linus WALLEIJ <linus.walleij@stericsson•com>,
Russell King <rmk@arm•linux.org.uk>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: FW: next build fails
Date: Thu, 16 Sep 2010 15:08:55 -0700 [thread overview]
Message-ID: <1284674935.2411.54.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100917080439.7c35775a.sfr@canb.auug.org.au>
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.
Daniel
next prev parent reply other threads:[~2010-09-16 22:09 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 [this message]
2010-09-17 10:35 ` Russell King
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=1284674935.2411.54.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@fifo99$(echo .)com \
--cc=linus.walleij@stericsson$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sundar.iyer@stericsson$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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