public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [LINK FAILURE] 2.5.12-dj1 (mark_buffer_uptodate)
Date: Fri, 3 May 2002 13:42:08 -0500	[thread overview]
Message-ID: <20020503184208.GA25124@local.enodev.com> (raw)
In-Reply-To: <20020503181719.GA20588@local.enodev.com> <20020503203752.C30500@suse.de>

Thanks. Just seconds ago, I looked at the various clues in
patch-2.5.12.bz2 on what exactly I had to do. Kindof a no-brainer for me
to be asking about.

Didn't know .13 was out. I'll have to run that one instead, as I have
been noticing .12 getting lots of reports on various things.

Trying to track linux-current again is always a fun adventure! Thanks!

On 05/03, Dave Jones said something like:
> On Fri, May 03, 2002 at 01:17:19PM -0500, Shawn wrote:
>  > Searched the archives, and didn't find anything.
>  > 
>  > Could someone point me in the right direction to get this compiled?
>  > 
>  > drivers/block/block.o(.text+0xc514): undefined reference to `mark_buffer_uptodate'
>  
> I'm creating the 2.5.13-dj1 diff this minute, so that should be up real
> soon now, which fixes this.  If you can't wait that long 8-), the fix is
> to change that line to read set_buffer_uptodate(tmp);
> 
> -- 
> | Dave Jones.        http://www.codemonkey.org.uk
> | SuSE Labs
--
Shawn Leas
core@enodev.com

I got food poisoning today.  I don't know when I'll use it.
						-- Stephen Wright

      reply	other threads:[~2002-05-03 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 18:17 [LINK FAILURE] 2.5.12-dj1 (mark_buffer_uptodate) Shawn
2002-05-03 18:36 ` Shawn
2002-05-03 18:37 ` Dave Jones
2002-05-03 18:42   ` Shawn [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=20020503184208.GA25124@local.enodev.com \
    --to=core@enodev.com \
    --cc=davej@suse.de \
    --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