linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Noriyuki Fujii <n-fujii@np.css.fujitsu.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: megaraidlinux@lsi.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2nd try] PCI legacy I/O port free driver - Making MegaRAID SAS driver
Date: Tue, 01 Dec 2009 10:15:34 +0900	[thread overview]
Message-ID: <4B146E36.7080506@np.css.fujitsu.com> (raw)
In-Reply-To: <1259614182.11762.5.camel@mulgrave.site>

James,

 > I need a Signed-off-by for this (see Documentation/SubmittingPatches).

 > This is taking away a tab and substituting spaces ... our style is to
 > use tabs.  You can run the patch through scripts/checkpatch.pl and it
 > will advise on problems like this.

I've already posted the patch obeying the community rules.
Could you see the following URL?

http://marc.info/?l=linux-scsi&m=125870212508167&w=2

Thanks,
Noriyuki Fujii

> On Wed, 2009-10-14 at 10:03 +0900, Noriyuki Fujii wrote:
>> Hi,
>>
>> Here's my 2nd try of the following post.
>>
>> http://marc.info/?l=linux-scsi&m=124962265606425&w=2
>>
>> I made a patch for MegaRAID sas driver to make PCI legacy I/O port free.
>>
>> The way to make PCI legacy I/O port free is the same as Fusion-MPT
>> driver's and it has been merged into 2.6.30.4.
>>
>> This has already been fixed in e1000 and lpfc.
>>
>> As a result of the above, the driver can handle its device even when
>> there are a huge number of PCI devices being used on the system and no
>> I/O port region assigned to the device.
>>
>> I'm not in the linux-scsi mailing list.
>> Please reply to the following address.
> 
> I need a Signed-off-by for this (see Documentation/SubmittingPatches).
> 
>>  E-Mail: n-fujii@np.css.fujitsu.com
>>
>> Thanks,
>> Noriyuki Fujii
>>
>> plain text document attachment
>> (linux-2.6-scsi-megaraid-sas-make-legacy-i-o-port-free.patch)
>> --- megaraid_sasOrg.c	2009-07-02 16:31:17.000000000 +0900
>> +++ megaraid_sasMod.c	2009-08-06 11:24:42.000000000 +0900
>> @@ -2573,7 +2573,9 @@ static int megasas_init_mfi(struct megas
>>  		instance->base_addr = pci_resource_start(instance->pdev, 0);
>>  	}
>>  
>> -	if (pci_request_regions(instance->pdev, "megasas: LSI")) {
>> +        if (pci_request_selected_regions(instance->pdev,
> 
> This is taking away a tab and substituting spaces ... our style is to
> use tabs.  You can run the patch through scripts/checkpatch.pl and it
> will advise on problems like this.
> 
> James
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 



      reply	other threads:[~2009-12-01  1:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  1:03 [PATCH 2nd try] PCI legacy I/O port free driver - Making MegaRAID SAS driver Noriyuki Fujii
2009-11-30 19:14 ` Yang, Bo
2009-11-30 20:49 ` James Bottomley
2009-12-01  1:15   ` Noriyuki Fujii [this message]

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=4B146E36.7080506@np.css.fujitsu.com \
    --to=n-fujii@np.css.fujitsu.com \
    --cc=James.Bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=megaraidlinux@lsi.com \
    /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).