From: "chia" <liuc@ceat.okstate.edu>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re:
Date: Tue, 21 Aug 2007 23:18:51 -0500 [thread overview]
Message-ID: <006101c7e473$8b924760$a378c00a@chia> (raw)
In-Reply-To: 46CBA353.7090108@gmail.com
Dear Tejun, Is 10.3 beta stable? Do I still need to patch it? If I do, what
version I should use? Can I apply a higher version patch to lower version of
kernel? Thanks!
--------------------------------------------------------------
Chia-Ming Liu, Ph.D.
Mixed Signal VLSI Design Group
Advanced Technology Research Center 235
Oklahoma State University
Website: http://msvlsi.okstate.edu
US Mail: 202 Engineering South Stillwater, OK 74078
Phone: 405-744-1662, 405-744-6241
Fax: 405-744-9198
----- Original Message -----
From: "Tejun Heo" <htejun@gmail.com>
To: "chia-ming liu" <chiaming.liu@gmail.com>
Cc: <linux-ide@vger.kernel.org>; <liuc@okstate.edu>
Sent: Tuesday, August 21, 2007 9:45 PM
Subject: Re:
> chia-ming liu wrote:
>> Dear Tejun, I am not very good at linux and just enough to get by. I
>> have tried to use your patch by issuing the command 'patch -p1 <
>> combined.patch' and I receive this
>>
>> msvlsi63:~/libata-tj-2.6.18.1-20061020 # patch -p1 < combined.patch
>> can't find file to patch at input line 5
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |Index: work/drivers/scsi/Kconfig
>> |===================================================================
>> |--- work.orig/drivers/scsi/Kconfig 2006-10-20 10:48:25.000000000
>> +0900
>> |+++ work/drivers/scsi/Kconfig 2006-10-20 10:48:35.000000000 +0900
>> --------------------------
>> File to patch:
>>
>> Then, I opened combined.path and look for line 5
>>
>> source "drivers/scsi/megaraid/Kconfig.megaraid"
>>
>> which point out the file I don't have. Am I missing something? I have
>> Opensuse 10.2 and Norco DS-1220 disk array which has Silicon Image
>> 3726 port multiplier.
>>
>> I don't have any driver install but Suse has recognized the PCI card
>> with Silicon Image 3124.
>
> OpenSUSE 10.3 Beta contains PMP support. I think that will be easier.
>
> --
> tejun
>
next prev parent reply other threads:[~2007-08-22 4:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 1:40 (unknown), chia-ming liu
2007-08-22 2:45 ` Tejun Heo
2007-08-22 4:18 ` chia [this message]
2007-08-22 4:22 ` Re: Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2017-11-13 14:55 Re: Amos Kalonzo
2017-05-03 6:23 Re: H.A
2017-02-23 15:09 Qin's Yanjun
2015-08-19 13:01 christain147
2012-05-22 14:39 Re: skoffman
2009-12-19 16:02 OFFICE OF THE SENATE
2009-09-14 20:54 Grant Grundler
[not found] <004c01c7ef32$0460e250$710a0a0a@GTDEV05>
2007-09-11 1:45 ` Re: Tejun Heo
2005-09-06 7:15 (unknown), Riccardo Castellani
2005-09-06 7:59 ` Stefan
2005-09-06 8:27 ` Re: Riccardo Castellani
2005-09-06 11:00 ` Re: Stefan
2005-09-07 8:30 ` Re: Riccardo Castellani
2005-09-07 9:28 ` Re: Erik Slagter
2005-09-08 1:21 ` Re: Stefan
2005-09-08 7:21 ` Re: Riccardo Castellani
2005-09-08 8:06 ` Re: Stefan
2005-09-08 11:34 ` Re: Riccardo Castellani
2005-09-08 15:55 ` Re: Stefan
2004-03-17 18:08 (unknown) yue-feng sun
2004-03-17 18:38 ` Bartlomiej Zolnierkiewicz
2004-03-17 20:43 ` Re: Ian Hastie
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='006101c7e473$8b924760$a378c00a@chia' \
--to=liuc@ceat.okstate.edu \
--cc=htejun@gmail.com \
--cc=linux-ide@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