public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hinds <dhinds@valinux.com>
To: "Jeff V. Merkey" <jmerkey@timpanogas.org>
Cc: David Ford <david@linux.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: current snapshots of pcmcia
Date: Mon, 6 Nov 2000 15:54:48 -0800	[thread overview]
Message-ID: <20001106155448.C19860@valinux.com> (raw)
In-Reply-To: <3A06757F.3C63F1A8@linux.com> <20001106104927.A19573@valinux.com> <3A073C8D.B6511746@linux.com> <20001106154039.A19860@valinux.com> <3A0742B0.653A5AAF@timpanogas.org>
In-Reply-To: <3A0742B0.653A5AAF@timpanogas.org>; from Jeff V. Merkey on Mon, Nov 06, 2000 at 04:45:52PM -0700

On Mon, Nov 06, 2000 at 04:45:52PM -0700, Jeff V. Merkey wrote:
> 
> On a related topic, I've pulled down your stuff at sourceforge and we
> are using it for our 2.4 build.  Is this the baest place or do you have
> somewhere more recent and is this the list to report bugs?  We have seen
> some problems with IBM thinkpads with DSP devices having some issues
> (like the volume control doesn't work right on 2.4).  Most are just
> annoyances and what I would classify as level IV bugs (very
> non-critical).

The sourceforge site is the most up to date place for PCMCIA.  That is
the best place to report bugs that are specific to that code.  For
bugs that are specific to things in the 2.4 tree and/or have to do
with how PCMCIA interacts with other subsystems (i.e., the problem
that started this thread, where I think the problem is in the PCI
subsystem), then linux-kernel is probably a better place.

-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-06 23:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A06757F.3C63F1A8@linux.com>
     [not found] ` <20001106104927.A19573@valinux.com>
2000-11-06 23:19   ` current snapshots of pcmcia David Ford
2000-11-06 23:40     ` David Hinds
2000-11-06 23:45       ` Jeff V. Merkey
2000-11-06 23:54         ` David Hinds [this message]
2000-11-07  0:16           ` Jeff V. Merkey
2000-11-07  0:19       ` David Ford
2000-11-07  0:31         ` David Hinds
2000-11-07  0:39           ` David Ford
2000-11-08 20:21       ` PCMCIA versioning Simon Huggins

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=20001106155448.C19860@valinux.com \
    --to=dhinds@valinux.com \
    --cc=david@linux.com \
    --cc=jmerkey@timpanogas.org \
    --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