From: Andrew Morton <akpm@osdl.org>
To: Shawn <core@enodev.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm1: Can't mount root
Date: Mon, 28 Jul 2003 22:47:56 -0700 [thread overview]
Message-ID: <20030728224756.56912a08.akpm@osdl.org> (raw)
In-Reply-To: <1059456725.4781.9.camel@localhost>
Shawn <core@enodev.com> wrote:
>
> > What was the most recent kernel which works?
>
> Looks like vanilla -test2 passes muster. Boots, etc.
drat, so I have a dud patch.
The simplest but boringest way to find it is a binary search through the
patches. The `series' file holds the patching order. it'd be painful
without using the scripts though.
You could try randomly reverting nforce2-acpi-fixes.patch.
next prev parent reply other threads:[~2003-07-29 5:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 21:43 2.6.0-test2-mm1: Can't mount root Shawn
2003-07-28 21:47 ` Andrew Morton
2003-07-28 22:06 ` Shawn
2003-07-28 22:02 ` Andrew Morton
2003-07-28 22:39 ` Shawn
2003-07-29 2:04 ` Shawn
2003-07-29 2:36 ` Andrew Morton
2003-07-29 4:44 ` Shawn
2003-07-29 5:32 ` Shawn
2003-07-29 5:47 ` Andrew Morton [this message]
2003-07-29 6:14 ` Shawn
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=20030728224756.56912a08.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=core@enodev.com \
--cc=linux-kernel@vger.kernel.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).