From: Paul Mackerras <paulus@samba.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: powerpc commits for 2.6.24
Date: Fri, 12 Oct 2007 08:31:54 +1000 [thread overview]
Message-ID: <18190.42074.495464.74585@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <3A203D25-2CC1-4450-ADA1-752A99504108@kernel.crashing.org>
Kumar Gala writes:
> I'm debugging one issue with MPC8560 that should get fixed today with
> a new pull request after I find the issue.
There's no particular hurry for bug fixes.
> Just to clarify, are we closing 2.6.24 for new code after you send
> Linus a pull request or are we still taking things during the two
> week merge window?
Basically, yes. We got a lecture at kernel summit from Linus and
Andrew where we got told to get everything merged early in the merge
window. I might make an exception for stuff that has already been
posted for review but still needs some minor changes, but other than
that, the window for new code has closed.
Paul.
next prev parent reply other threads:[~2007-10-11 22:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 12:30 powerpc commits for 2.6.24 Paul Mackerras
2007-10-11 12:47 ` Josh Boyer
2007-10-11 22:07 ` Josh Boyer
2007-10-12 8:41 ` Stefan Roese
2007-10-11 12:52 ` Kumar Gala
2007-10-11 12:53 ` Paul Mackerras
2007-10-11 13:14 ` Kumar Gala
2007-10-11 20:55 ` Benjamin Herrenschmidt
2007-10-11 21:06 ` Kumar Gala
2007-10-11 13:19 ` Kumar Gala
2007-10-11 14:16 ` Grant Likely
2007-10-11 15:36 ` Timur Tabi
2007-10-11 17:06 ` Arnd Bergmann
2007-10-11 22:31 ` Paul Mackerras [this message]
2007-10-11 22:51 ` Kumar Gala
2007-10-11 14:29 ` Grant Likely
2007-10-11 16:58 ` Olof Johansson
2007-10-12 0:28 ` Michael Ellerman
2007-10-12 0:32 ` Paul Mackerras
2007-10-12 0:37 ` Michael Ellerman
2007-10-12 2:36 ` David Gibson
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=18190.42074.495464.74585@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).