From: Christopher Curtis <chris.curtis@riptidesoftware.com>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Cc: daniel.ritz@gmx.ch
Subject: Re: 2.4.22-rc2 PCMCIA problems
Date: Fri, 22 Aug 2003 07:42:29 -0400 [thread overview]
Message-ID: <3F4601A5.6010600@riptidesoftware.com> (raw)
In a message I wrote but didn't get because I'm not on the mailing list,
I wrote:
> I've been using kernel 2.4.22-pre6 with the smbfs LFS patch and the
[...]
> However, with this new kernel, I can no longer 'modprobe airo_cs'
[...]
Naturally, this was the result of my own foolishness. I wanted to let
everyone know that there's no need to look into this, even though y'all
seem to have already deduced this. Everything appears to be working.
regards,
Chris
next reply other threads:[~2003-08-22 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 11:42 Christopher Curtis [this message]
2003-08-22 14:42 ` Running SMP 2.4.21 #2 SMP Kernel on single processor : Memory Leakage? Mehmet Ali Suzen
-- strict thread matches above, loose matches on Subject: below --
2003-08-22 0:03 2.4.22-rc2 PCMCIA problems Christopher Curtis
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=3F4601A5.6010600@riptidesoftware.com \
--to=chris.curtis@riptidesoftware.com \
--cc=daniel.ritz@gmx.ch \
--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