The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Barry K. Nathan" <barryn@pobox.com>
To: 1qay beer <1qay@beer.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX
Date: Mon, 2 Jan 2006 06:28:44 -0800	[thread overview]
Message-ID: <986ed62e0601020628r3081fa52ld8c772c5b4a05ee2@mail.gmail.com> (raw)
In-Reply-To: <20060101173909.D30257B386@ws5-10.us4.outblaze.com>

Add my voice to the chorus of people who are having no problems with
their PDC20269's, for several years now (since 2002, I think -- and I
didn't have problems before then, I just didn't have a PDC20269
before).
--
-Barry K. Nathan <barryn@pobox.com>

  parent reply	other threads:[~2006-01-02 14:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-01 17:39 Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX 1qay beer
2006-01-01 17:56 ` Alistair John Strachan
2006-01-01 21:22 ` Joshua Kwan
2006-01-02  9:04   ` Pasi Kärkkäinen
2006-01-02 14:28 ` Barry K. Nathan [this message]
2006-01-02 22:35 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2006-01-06 11:41 1qay beer
2006-06-19 22:05 [patch 8/8] lock validator: add s390 to supported options Andrew Morton
2006-06-19 22:18 ` Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX Erik Ohrnberger
2006-06-20  8:20   ` Alan Cox
2006-06-20 12:52     ` Erik Ohrnberger
2006-06-21  1:19       ` Erik Ohrnberger
2006-06-21 10:51         ` Alan Cox
2006-06-21 13:09           ` Erik Ohrnberger
2006-06-21 13:34             ` Alan Cox
2006-06-21 13:34               ` Mike Snitzer
2006-06-21 14:07                 ` Alan Cox
2006-06-21 15:20                   ` Mike Snitzer
2006-06-21 16:10                     ` Alan Cox
2006-06-21 17:47                       ` Mike Snitzer

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=986ed62e0601020628r3081fa52ld8c772c5b4a05ee2@mail.gmail.com \
    --to=barryn@pobox.com \
    --cc=1qay@beer.com \
    --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