public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg.Chandler@wellsfargo.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH 1/1] drivers/block/Kconfig text update.  Try #2
Date: Mon, 13 Nov 2006 15:34:04 -0800	[thread overview]
Message-ID: <455900EC.4010107@oracle.com> (raw)
In-Reply-To: <E8C008223DD5F64485DFBDF6D4B7F71D02235904@msgswbmnmsp25.wellsfargo.com>

Greg.Chandler@wellsfargo.com wrote:
>  
> Sorry...
> I've attached the new one.

OK, thanks.

>> The second line of the drivers/block/cciss.c file says:
>>
>> " *    Disk Array driver for HP SA 5xxx and 6xxx Controllers"
>>
>> I couldn't find the 6 series anywhere in the menu, and I ended up 
>> finding it in the code...
> 
> Please read/observe Documentation/SubmittingPatches:
> the --- & +++ lines should begin with linux/drivers/... or a/drivers/...
> so that the patch can be applied with "patch -p1".
> 
>> --- drivers/block/Kconfig.old   2006-11-13 14:20:12.000000000 -0800
>> +++ drivers/block/Kconfig       2006-11-13 14:20:32.000000000 -0800
>> @@ -155,10 +155,10 @@
>>           this driver.
>>
>>  config BLK_CPQ_CISS_DA
>> -       tristate "Compaq Smart Array 5xxx support"
>> +       tristate "Compaq Smart Array 5xxx/6xxx support"
>>         depends on PCI
>>         help
>> -         This is the driver for Compaq Smart Array 5xxx controllers.
>> +         This is the driver for Compaq Smart Array 5xxx/6xxx
>> controllers.
> 
> Patch is line-wrapped on the line above.
> 
>>           Everyone using these boards should say Y here.
>>           See <file:Documentation/cciss.txt> for the current list of
>>           boards supported by this driver, and for further information
> 
> ---

-- 
~Randy

  reply	other threads:[~2006-11-13 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 23:22 [PATCH 1/1] drivers/block/Kconfig text update. Try #2 Greg.Chandler
2006-11-13 23:34 ` Randy Dunlap [this message]
2006-11-13 23:47 ` Jiri Slaby

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=455900EC.4010107@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Greg.Chandler@wellsfargo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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