All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Brown, Len" <len.brown@intel.com>
Subject: What's happening with the cpuidle code?
Date: Tue, 04 Sep 2007 16:47:30 -0400	[thread overview]
Message-ID: <46DDC462.2040309@redhat.com> (raw)

A look at the 'cpuidle' branch of git-acpi shows a commit
e40cede7d63a029e92712a3fe02faee60cc38fb4, "cpuidle: first
round of documentation updates" that doesn't show up in that
branch online. The entire Documentation/cpuidle directory
is missing from the tree when looking at the web pages, and
it's missing from git-acpi.patch in 2.6.23-rc4-mm1 (but the
patch shows up in the summary information in the patch
header.) Where did it go? And how can -mm be used to test
things if its patches don't even match their own headers?


             reply	other threads:[~2007-09-04 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 20:47 Chuck Ebbert [this message]
2007-09-04 21:43 ` What's happening with the cpuidle code? Len Brown
2007-09-04 22:15   ` Chuck Ebbert

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=46DDC462.2040309@redhat.com \
    --to=cebbert@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.