From: John Weber <weber@sixbit.org>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.71-mm1 PCMCIA Yenta socket nonfunctional
Date: Mon, 16 Jun 2003 12:12:06 -0400 [thread overview]
Message-ID: <3EEDEC56.8090802@sixbit.org> (raw)
In-Reply-To: <20030616110017$7e46@gated-at.bofh.it>
Michael Frank wrote:
>
>>Could you check whether plain 2.5.71 (or 2.5.71-bkcurr) works?
>
>
> 2.5.71 had a compile problem - posted seperately
> see 2.5.71 net/built-in.o : undefined reference to `register_cpu_notifier'
This has been fixed in the bk snapshots, so use 2.5.71-bkX.
next parent reply other threads:[~2003-06-16 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030616061004$261e@gated-at.bofh.it>
[not found] ` <20030616073013$5824@gated-at.bofh.it>
[not found] ` <20030616110017$7e46@gated-at.bofh.it>
2003-06-16 16:12 ` John Weber [this message]
2003-06-16 5:58 2.5.71-mm1 PCMCIA Yenta socket nonfunctional Michael Frank
2003-06-16 7:10 ` Michael Frank
2003-06-16 7:25 ` Russell King
2003-06-16 10:48 ` Michael Frank
2003-06-21 3:31 ` Michael Frank
2003-06-18 5:16 ` Michael Frank
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=3EEDEC56.8090802@sixbit.org \
--to=weber@sixbit.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
/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