From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Roland Dreier <rdreier@cisco•com>
Cc: linux-next@vger•kernel.org, Linus <torvalds@linux-foundation•org>,
LKML <linux-kernel@vger•kernel.org>,
general@lists•openfabrics.org
Subject: Re: [ofa-general] Re: linux-next: origin tree build failure
Date: Wed, 31 Dec 2008 02:46:54 +1100 [thread overview]
Message-ID: <20081231024654.a73f20df.sfr@canb.auug.org.au> (raw)
In-Reply-To: <adaljtxsma7.fsf@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Hi Roland,
On Tue, 30 Dec 2008 07:41:36 -0800 Roland Dreier <rdreier@cisco•com> wrote:
>
> > I can drop the revert after your fix goes into Linus' tree (since that is
> > where the breakage is) ... looking forward to it, thanks.
>
> Shouldn't it work if the fix is in my for-next branch, since you pull
> that as part of the -next tree? Or am I unclear on how -next works?
I also build the tree between merging most of the trees (including after
fetching Linus' latest tree).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-30 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 0:43 linux-next: origin tree build failure Stephen Rothwell
2008-12-29 3:36 ` Roland Dreier
2008-12-29 3:44 ` Roland Dreier
2008-12-29 9:58 ` Aleksey Senin
2008-12-29 16:13 ` [ofa-general] " Roland Dreier
2008-12-29 16:52 ` Aleksey Senin
2008-12-29 20:18 ` Roland Dreier
2008-12-29 21:07 ` Linus Torvalds
2008-12-29 21:35 ` Roland Dreier
2008-12-29 21:48 ` Roland Dreier
2008-12-29 8:48 ` Aleksey Senin
2008-12-30 7:38 ` Roland Dreier
2008-12-30 8:30 ` Stephen Rothwell
2008-12-30 15:41 ` Roland Dreier
2008-12-30 15:46 ` Stephen Rothwell [this message]
2008-12-30 22:52 ` Stephen Rothwell
2008-12-30 22:56 ` Roland Dreier
2008-12-30 23:17 ` Stephen Rothwell
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=20081231024654.a73f20df.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=general@lists$(echo .)openfabrics.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdreier@cisco$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/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