From: David Woodhouse <dwmw2@infradead.org>
To: Jim Nelson <james4765@verizon.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 2.6.8.1 compile failed.
Date: Fri, 01 Oct 2004 10:05:44 +0100 [thread overview]
Message-ID: <1096621544.4828.9.camel@localhost.localdomain> (raw)
In-Reply-To: <415CD869.7070607@verizon.net>
On Fri, 2004-10-01 at 00:09 -0400, Jim Nelson wrote:
> A question from a relative newbie (just getting started in kernel
> hacking) - is there a focus on 2.6 development exclusively in this list
> or is there some attempt to maintain 2.4 compatibility? Although I can
> understand either way, I'd like to know if there needs to be an effort
> to maintain backwards compatibility.
There's maybe an _attempt_ but no _effort_. That is; if we can easily
choose to make changes in a way which doesn't make it break on 2.4 we
will, but we won't go to any _trouble_.
The 2.4 kernel is an old, stable kernel. If it works for you that's
great and you should continue using it. If it _doesn't_ then you should
be using 2.6.
> Patch to drivers/mtd/chips/amd_flash.c included.
I left that broken on purpose. That driver has been obsoleted by
jedec_probe and the CFI command set driver.
--
dwmw2
prev parent reply other threads:[~2004-10-01 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 4:09 2.6.8.1 compile failed Jim Nelson
2004-10-01 9:05 ` David Woodhouse [this message]
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=1096621544.4828.9.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=james4765@verizon.net \
--cc=linux-mtd@lists.infradead.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