linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel Lao" <laodx@gzjpg.com>
To: Gabriel Paubert <paubert@iram.es>,
	linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: A question about the 68-pin SCSI devices
Date: Wed, 6 Nov 2002 8:39:11 +0800	[thread overview]
Message-ID: <20021106092862.SM00332@xuyf> (raw)


Thanks for your answer.
Yes, I use 2.2.12 because of the VME driver! I am too lazy to compile a latest kernel :-( , and not sure if I must get a VME patch for the new kernel to support it.
May you help me to make a better choice?

>It should work right out of the box.
>
>But why are you still using 2.2.12, because you use my VME driver ?

---
Daniel Lao

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-11-06  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  0:39 Daniel Lao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05  4:16 A question about the 68-pin SCSI devices Daniel Lao
2002-11-05 16:47 ` Gabriel Paubert

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=20021106092862.SM00332@xuyf \
    --to=laodx@gzjpg.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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;
as well as URLs for NNTP newsgroup(s).