From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Woodhouse <dwmw2@infradead•org>
Cc: linux-next@vger•kernel.org,
Jaswinder Singh <jaswinder@infradead•org>,
David Miller <davem@davemloft•net>
Subject: Re: linux-next: sparc/firmware build failure
Date: Tue, 28 Oct 2008 23:07:34 +1100 [thread overview]
Message-ID: <20081028230734.7d2bba2f.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1225194154.18031.185.camel@macbook.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Hi David,
On Tue, 28 Oct 2008 11:42:34 +0000 David Woodhouse <dwmw2@infradead•org> wrote:
>
> On Tue, 2008-10-28 at 21:45 +1100, Stephen Rothwell wrote:
> > I have now been carrying this patch since September 1. David (W), are
> > going to pick it up, please? This should be put into the firmware tree
> > as part of the merge commit merging Linus' current tree.
>
> I'll merge it; thanks.
Thanks.
> > Incidentally, what is to be the fate of the rest of the firmware tree?
>
> We're planning to get the patches in for 2.6.29.
OK.
> I told Dave that I'd hold off on the network bits until the first round
> of patches had been shipped successfully -- so putting them into
> 2.6.28-rc within _days_ of the 2.6.27 release didn't seem to be the
> right thing to do.
Yeah.
--
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-10-28 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 9:10 linux-next: sparc/firmware build failure Stephen Rothwell
2008-09-01 9:46 ` David Miller
2008-10-28 10:45 ` Stephen Rothwell
2008-10-28 11:42 ` David Woodhouse
2008-10-28 12:07 ` Stephen Rothwell [this message]
2008-11-03 3:55 ` Stephen Rothwell
2008-11-05 6:02 ` Stephen Rothwell
2008-11-06 2:44 ` Stephen Rothwell
2008-11-13 3:35 ` Stephen Rothwell
2008-11-13 6:57 ` David Miller
2008-11-18 15:37 ` David Woodhouse
2008-11-18 20:09 ` 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=20081028230734.7d2bba2f.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=dwmw2@infradead$(echo .)org \
--cc=jaswinder@infradead$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.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