From: "Kevin Liao" <kevinliao@wellsyn.com>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: compile error (undefined reference to jffs2_getlink) for kernel 2.4.26
Date: Thu, 3 Mar 2005 19:59:46 +0800 [thread overview]
Message-ID: <027b01c51fe8$7f7624d0$1b0a060a@WellSyn.org> (raw)
In-Reply-To: Pine.LNX.4.58.0503031136030.26599@phoenix.infradead.org
> Kevin,
>
> I'm sorry, that was my patch which broke 2.4. I've completely forgotten
> about 2.4-compatibility. I'll see what I might do to repair this.
> Apologies.
>
> --
> Best Regards,
> Artem B. Bityuckiy,
> St.-Petersburg, Russia.
>
You do not need to be sorry at all. I really don't want you guys to
maintain the backward compatibility for 2.4.x. I just want to find
the reason why this snapshop breaks 2.4.x and try to fix it by
myself. I need to say thank to tglx. Because his help, I now have
a working 2.4.x kernel with snapshop 20050228:) And I totally
agree his suggestion for removing the 2.4.x code from current CVS.
Regards,
Kevin
next prev parent reply other threads:[~2005-03-03 12:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 4:52 compile error (undefined reference to jffs2_getlink) for kernel 2.4.26 Kevin Liao
2005-03-03 8:28 ` Thomas Gleixner
2005-03-03 8:40 ` compile error (undefined reference to jffs2_getlink) forkernel 2.4.26 Kevin Liao
2005-03-03 9:01 ` Thomas Gleixner
2005-03-03 15:36 ` Steve Wahl
2005-03-03 17:06 ` Thomas Gleixner
2005-03-03 11:36 ` compile error (undefined reference to jffs2_getlink) for kernel 2.4.26 Artem B. Bityuckiy
2005-03-03 11:59 ` Kevin Liao [this message]
2005-03-03 12:19 ` Artem B. Bityuckiy
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='027b01c51fe8$7f7624d0$1b0a060a@WellSyn.org' \
--to=kevinliao@wellsyn.com \
--cc=dedekind@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox