linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH] Correct a terrible scheduling error
Date: Tue,  4 Mar 2008 04:42:07 +0100	[thread overview]
Message-ID: <d1f2621db926ece5ec9ec0baf8a70ec8e2d72b10.1204601394.git.segher@kernel.crashing.org> (raw)

It would be a pity if we can't all enjoy this.

Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
---
 Documentation/feature-removal-schedule.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index c1d1fd0..78021bf 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -201,13 +201,13 @@ Who:  Tejun Heo <htejun@gmail.com>
 ---------------------------
 
 What: The arch/ppc and include/asm-ppc directories
-When: Jun 2008
+When: end of July 2008
 Why:  The arch/powerpc tree is the merged architecture for ppc32 and ppc64
       platforms.  Currently there are efforts underway to port the remaining
       arch/ppc platforms to the merged tree.  New submissions to the arch/ppc
       tree have been frozen with the 2.6.22 kernel release and that tree will
       remain in bug-fix only mode until its scheduled removal.  Platforms
-      that are not ported by June 2008 will be removed due to the lack of an
+      that are not ported by July 2008 will be removed due to the lack of an
       interested maintainer.
 Who:  linuxppc-dev@ozlabs.org
 
-- 
1.5.3.4.208.g805a

                 reply	other threads:[~2008-03-04  3:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=d1f2621db926ece5ec9ec0baf8a70ec8e2d72b10.1204601394.git.segher@kernel.crashing.org \
    --to=segher@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).