From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: More commits added to powerpc.git next and master branches
Date: Tue, 16 Dec 2008 20:07:45 +1100 [thread overview]
Message-ID: <1229418465.7319.14.camel@pasglop> (raw)
In-Reply-To: <18759.28289.218980.817708@cargo.ozlabs.ibm.com>
On Tue, 2008-12-16 at 20:01 +1100, Paul Mackerras wrote:
> > Is there any reason you haven't been updating patchwork ? Or are you
> > waiting for things in your -next branch to actually hit upstream ?
>
> Just an oversight. I have updated it now, at least for the patches I
> committed.
Cool, thanks. It's getting a little bit out of control, hence my
asking :-)
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-16 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 5:10 More commits added to powerpc.git next and master branches Paul Mackerras
2008-12-16 7:04 ` Benjamin Herrenschmidt
2008-12-16 9:01 ` Paul Mackerras
2008-12-16 9:07 ` Benjamin Herrenschmidt [this message]
2008-12-16 11:33 ` Peter Korsgaard
2008-12-16 16:28 ` Josh Boyer
2008-12-17 3:33 ` Paul Mackerras
2008-12-16 16:38 ` Anton Vorontsov
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=1229418465.7319.14.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).