All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Saxena <sumit.saxena@broadcom.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	kashyap.desai@avagotech.com, sumit.saxena@avagotech.com,
	uday.lingala@avagotech.com, jejb@linux.vnet.ibm.com,
	martin.petersen@oracle.com
Cc: megaraidlinux.pdl@avagotech.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: RE: [PATCH] megaraid_sas: Fix the search of first memory bar
Date: Fri, 26 Aug 2016 09:31:19 +0530	[thread overview]
Message-ID: <c0561d5e1fa756c46d2eafa2c0b8dc09@mail.gmail.com> (raw)
In-Reply-To: <1471768105-14730-1-git-send-email-christophe.jaillet@wanadoo.fr>

>-----Original Message-----
>From: Christophe JAILLET [mailto:christophe.jaillet@wanadoo.fr]
>Sent: Sunday, August 21, 2016 1:58 PM
>To: kashyap.desai@avagotech.com; sumit.saxena@avagotech.com;
>uday.lingala@avagotech.com; jejb@linux.vnet.ibm.com;
>martin.petersen@oracle.com
>Cc: megaraidlinux.pdl@avagotech.com; linux-scsi@vger.kernel.org; linux-
>kernel@vger.kernel.org; kernel-janitors@vger.kernel.org; Christophe JAILLET
>Subject: [PATCH] megaraid_sas: Fix the search of first memory bar
>
>The 2nd parameter of 'find_first_bit' is the number of bits to search.
>In this case, we are passing 'sizeof(unsigned long)' which is likely to be
>4.
>
>It is likely that the number of bits in a long was expected here, so use
>BITS_PER_LONG instead.
>
>Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>---
>Other options are possible:
>  - 'bar_list' being a 'unsigned long', use __ffs to reduce code verbosity
>  - PCI_NUM_RESOURCES, which is the maximum number of bits that can be set
>    by 'pci_select_bars()'
>---
> drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
>b/drivers/scsi/megaraid/megaraid_sas_base.c
>index c1ed25adb17e..7d3de811d33c 100644
>--- a/drivers/scsi/megaraid/megaraid_sas_base.c
>+++ b/drivers/scsi/megaraid/megaraid_sas_base.c
>@@ -5036,7 +5036,7 @@ static int megasas_init_fw(struct megasas_instance
>*instance)
>
> 	/* Find first memory bar */
> 	bar_list = pci_select_bars(instance->pdev, IORESOURCE_MEM);
>-	instance->bar = find_first_bit(&bar_list, sizeof(unsigned long));
>+	instance->bar = find_first_bit(&bar_list, BITS_PER_LONG);
> 	if (pci_request_selected_regions(instance->pdev, 1<<instance->bar,
> 					 "megasas: LSI")) {
> 		dev_printk(KERN_DEBUG, &instance->pdev->dev, "IO memory
>region busy!\n");

Acked by: Sumit Saxena <sumit.saxena@broadcom.com>

>--
>2.7.4
>
>
>---
>L'absence de virus dans ce courrier électronique a été vérifiée par le
>logiciel
>antivirus Avast.
>https://www.avast.com/antivirus

WARNING: multiple messages have this Message-ID (diff)
From: Sumit Saxena <sumit.saxena@broadcom.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	kashyap.desai@avagotech.com, sumit.saxena@avagotech.com,
	uday.lingala@avagotech.com, jejb@linux.vnet.ibm.com,
	martin.petersen@oracle.com
Cc: megaraidlinux.pdl@avagotech.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: RE: [PATCH] megaraid_sas: Fix the search of first memory bar
Date: Fri, 26 Aug 2016 04:13:19 +0000	[thread overview]
Message-ID: <c0561d5e1fa756c46d2eafa2c0b8dc09@mail.gmail.com> (raw)
In-Reply-To: <1471768105-14730-1-git-send-email-christophe.jaillet@wanadoo.fr>

>-----Original Message-----
>From: Christophe JAILLET [mailto:christophe.jaillet@wanadoo.fr]
>Sent: Sunday, August 21, 2016 1:58 PM
>To: kashyap.desai@avagotech.com; sumit.saxena@avagotech.com;
>uday.lingala@avagotech.com; jejb@linux.vnet.ibm.com;
>martin.petersen@oracle.com
>Cc: megaraidlinux.pdl@avagotech.com; linux-scsi@vger.kernel.org; linux-
>kernel@vger.kernel.org; kernel-janitors@vger.kernel.org; Christophe JAILLET
>Subject: [PATCH] megaraid_sas: Fix the search of first memory bar
>
>The 2nd parameter of 'find_first_bit' is the number of bits to search.
>In this case, we are passing 'sizeof(unsigned long)' which is likely to be
>4.
>
>It is likely that the number of bits in a long was expected here, so use
>BITS_PER_LONG instead.
>
>Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>---
>Other options are possible:
>  - 'bar_list' being a 'unsigned long', use __ffs to reduce code verbosity
>  - PCI_NUM_RESOURCES, which is the maximum number of bits that can be set
>    by 'pci_select_bars()'
>---
> drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
>b/drivers/scsi/megaraid/megaraid_sas_base.c
>index c1ed25adb17e..7d3de811d33c 100644
>--- a/drivers/scsi/megaraid/megaraid_sas_base.c
>+++ b/drivers/scsi/megaraid/megaraid_sas_base.c
>@@ -5036,7 +5036,7 @@ static int megasas_init_fw(struct megasas_instance
>*instance)
>
> 	/* Find first memory bar */
> 	bar_list = pci_select_bars(instance->pdev, IORESOURCE_MEM);
>-	instance->bar = find_first_bit(&bar_list, sizeof(unsigned long));
>+	instance->bar = find_first_bit(&bar_list, BITS_PER_LONG);
> 	if (pci_request_selected_regions(instance->pdev, 1<<instance->bar,
> 					 "megasas: LSI")) {
> 		dev_printk(KERN_DEBUG, &instance->pdev->dev, "IO memory
>region busy!\n");

Acked by: Sumit Saxena <sumit.saxena@broadcom.com>

>--
>2.7.4
>
>
>---
>L'absence de virus dans ce courrier électronique a été vérifiée par le
>logiciel
>antivirus Avast.
>https://www.avast.com/antivirus

  parent reply	other threads:[~2016-08-26  4:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21  8:28 [PATCH] megaraid_sas: Fix the search of first memory bar Christophe JAILLET
2016-08-21  8:28 ` Christophe JAILLET
2016-08-26  2:30 ` Martin K. Petersen
2016-08-26  2:30   ` Martin K. Petersen
2016-08-26  4:01 ` Sumit Saxena [this message]
2016-08-26  4:13   ` Sumit Saxena
2016-08-31  2:23 ` Martin K. Petersen
2016-08-31  2:23   ` Martin K. Petersen

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=c0561d5e1fa756c46d2eafa2c0b8dc09@mail.gmail.com \
    --to=sumit.saxena@broadcom.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=kashyap.desai@avagotech.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=megaraidlinux.pdl@avagotech.com \
    --cc=sumit.saxena@avagotech.com \
    --cc=uday.lingala@avagotech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.