public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Kevin Liao <kevinliao@wellsyn.com>
Cc: MTD List <linux-mtd@lists.infradead.org>
Subject: Re: compile error (undefined reference to jffs2_getlink) forkernel 2.4.26
Date: Thu, 03 Mar 2005 10:01:27 +0100	[thread overview]
Message-ID: <1109840487.5398.16.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <01e801c51fcc$ae93fa10$1b0a060a@WellSyn.org>

On Thu, 2005-03-03 at 16:40 +0800, Kevin Liao wrote:
> Thanks for the reply. Actully I had read it before I ask this question.
> According to the webpage, the kernel version I used should be ok.
> I think the root cause is not the kernel version. Because I serach
> the whole directory extracted from snapshop 20050302 but found
> no implementation for jffs2_getlink function. Maybe I search the
> wrong place?

Yes, jffs2_getlink is removed. There was an update to jffs2 a couple of
days ago. It broke the 2.4 code.

Frankly spoken, I personally don't care.

2.4 is as is and we are not going to do anything about. Feel free to fix
it by porting the link changes back to super-v24.c or use an snapshot
before said changes.

tglx

  reply	other threads:[~2005-03-03  9:01 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 [this message]
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
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=1109840487.5398.16.camel@tglx.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=kevinliao@wellsyn.com \
    --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