From: Jonas Holmberg <jonas.holmberg@axis.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Device ID collision in amd_flash.c
Date: Thu, 3 Feb 2005 11:55:05 +0100 [thread overview]
Message-ID: <20050203105505.GB20345@axis.com> (raw)
In-Reply-To: <1107426233.12383.46.camel@localhost.localdomain>
On Thu, Feb 03, 2005 at 10:23:52AM +0000, David Woodhouse wrote:
> On Thu, 2005-02-03 at 10:58 +0100, Jonas Holmberg wrote:
> > Silly me, who cares about obsolete drivers...
> > Let me rephrase that question: Any objections before I commit on
> > friday (tomorrow)?
>
> Sorry, go ahead.
Thanks.
>
> > I still would like to know how bugfixes finds their way into Linux
> > 2.4. As I understand, the main trunk in CVS is for 2.6 and I can't
> > find any 2.4-branch...
>
> In general, they don't get in to 2.4. Nobody cares about 2.4 any more.
> If it _works_ for you, all well and good. But if it hasn't already been
> working for you for a year, then why are you trying to make it work now?
I just noticed the bug. It only reveals itself when you try to erase
the first sector on that particular chip, and we never had to do that,
until now.
> Use 2.6.
Will do, but need bugfix for old stuff too.
It would be quite nice with a 2.4-branch that we can commit bugfixes
to that could be sent to Marcelo regularly. But if I'm the first to
ask, we probably don't need it.
>
> Feel free to send this change to Marcelo if you really care.
OK.
/Jonas
next prev parent reply other threads:[~2005-02-03 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 11:07 Device ID collision in amd_flash.c Jonas Holmberg
2005-02-03 9:58 ` Jonas Holmberg
2005-02-03 10:23 ` David Woodhouse
2005-02-03 10:55 ` Jonas Holmberg [this message]
2005-02-03 11:24 ` David Woodhouse
2005-02-03 14:13 ` Josh Boyer
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=20050203105505.GB20345@axis.com \
--to=jonas.holmberg@axis.com \
--cc=dwmw2@infradead.org \
--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 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.