Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Miller <mike.miller@hp.com>
Cc: JensAxboejens.axboe@oracle.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2] cciss: fix regression in procfs display fw version, obsoletes previous patch 2 of 2
Date: Thu, 16 Oct 2008 14:56:42 -0700	[thread overview]
Message-ID: <20081016145642.2ba2adba.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081016215016.GB25704@roadking.ldev.net>

On Thu, 16 Oct 2008 16:50:16 -0500
Mike Miller <mike.miller@hp.com> wrote:

> 
> Patch 2 of 2
> 
> This patch obsoletes patch 2/2 from yesterday. It fixes a regression in
> procfs where the controller firmware version is not displayed. The previous
> patch also addressed the problem but the code would be called whenever
> anything changed on the array such as the number of logical volumes, etc.
> This patch only gets called once for each controller.
> Please consider this for inclusion.
> 

Again, this description doesn't contain enough information for us to
work out which kernels need patching.

> 
> diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
> index 0f367b1..efa5414 100644
> --- a/drivers/block/cciss.c
> +++ b/drivers/block/cciss.c
> @@ -3404,7 +3404,8 @@ static int __devinit cciss_init_one(struct pci_dev *pdev,
>  	int i;
>  	int j = 0;
>  	int rc;
> -	int dac;
> +	int dac, return_code;
> +	InquiryData_struct *inq_buff = NULL;

This initialisation is not needed.

>  	i = alloc_cciss_hba();
>  	if (i < 0)
> @@ -3510,6 +3511,25 @@ static int __devinit cciss_init_one(struct pci_dev *pdev,
>  	/* Turn the interrupts on so we can service requests */
>  	hba[i]->access.set_intr_mask(hba[i], CCISS_INTR_ON);
>  
> +	/* Get the firmware version */ 
> +	inq_buff = kzalloc(sizeof(InquiryData_struct), GFP_KERNEL);
> +        if (inq_buff == NULL) {
> +                printk(KERN_ERR "cciss: out of memory\n");

Whitespace is all screwed up.

> +                return ENOMEM;

Should be -ENOMEM.

> +        }
> +
> +	return_code = sendcmd_withirq(CISS_INQUIRY, i, inq_buff, 
> +		sizeof(InquiryData_struct), 0, 0 ,0, TYPE_CMD);
> +	if (return_code == IO_OK) {
> +		hba[i]->firm_ver[0] = inq_buff->data_byte[32];
> +		hba[i]->firm_ver[1] = inq_buff->data_byte[33];
> +		hba[i]->firm_ver[2] = inq_buff->data_byte[34];
> +		hba[i]->firm_ver[3] = inq_buff->data_byte[35];
> +	} else {	 /* send command failed */
> +		printk(KERN_WARNING "cciss: unable to determine firmware"
> +			" version of controller\n");
> +	}
> +
>  	cciss_procinit(i);
>  
>  	hba[i]->cciss_max_sectors = 2048;

  reply	other threads:[~2008-10-16 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 21:50 [PATCH 2/2] cciss: fix regression in procfs display fw version, obsoletes previous patch 2 of 2 Mike Miller
2008-10-16 21:56 ` Andrew Morton [this message]
2008-10-16 22:21   ` Miller, Mike (OS Dev)
2008-10-16 22:32     ` Alexey Dobriyan
2008-10-16 22:56       ` Miller, Mike (OS Dev)
2008-10-16 23:17         ` Alexey Dobriyan

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=20081016145642.2ba2adba.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=JensAxboejens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.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