From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ying Chu <jasonchu@marvell.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/4] mvsas: Fine-tuned tags array for alignment
Date: Fri, 08 May 2009 12:22:58 -0400 [thread overview]
Message-ID: <4A045C62.50404@garzik.org> (raw)
In-Reply-To: <1241795999.3327.38.camel@mulgrave.int.hansenpartnership.com>
James Bottomley wrote:
> On Fri, 2009-05-08 at 14:18 +0800, Ying Chu wrote:
>> >From 2269b0ff3c2573f76cb0569eb5da99e9f12711d1 Mon Sep 17 00:00:00 2001
>> From: ayan <ayan@marvell.com>
>> Date: Fri, 8 May 2009 19:59:39 +0800
>> Subject: [PATCH 4/4] bug fix: alignment
>>
>> Fine-tuned tags array with u32 for alignment.
>>
>> Signed-off-by: Ying Chu <jasonchu@marvell.com>
>> Signed-off-by: Andy Yan <ayan@marvell.com>
>> Signed-off-by: Ke Wei <kewei@marvell.com>
>> ---
>> drivers/scsi/mvsas/mv_sas.h | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/scsi/mvsas/mv_sas.h b/drivers/scsi/mvsas/mv_sas.h
>> index 75b9748..04f27bf 100644
>> --- a/drivers/scsi/mvsas/mv_sas.h
>> +++ b/drivers/scsi/mvsas/mv_sas.h
>> @@ -313,7 +313,7 @@ struct mvs_info {
>> const struct mvs_chip_info *chip;
>>
>> int tags_num;
>> - u8 tags[MVS_SLOTS >> 3];
>> + u32 tags[MVS_SLOTS >> 5];
>
> Why not just do
>
> DECLARE_BITMAP(tags, MVS_SLOTS);
>
> here? ... that way you're using the correctly defined type for the
> bitmap operations and you can lose the spurious (void *) cast in your
> bitmap wrapper operations.
Agreed. Type 'u32' is incorrect for bitmap operations... it needs to
be 'unsigned long', which is what DECLARE_BITMAP gives you.
Jeff
next prev parent reply other threads:[~2009-05-08 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 6:18 [PATCH 4/4] mvsas: Fine-tuned tags array for alignment Ying Chu
2009-05-08 15:19 ` James Bottomley
2009-05-08 16:22 ` Jeff Garzik [this message]
2009-05-09 6:52 ` Ying Chu
2009-05-09 6:52 ` Jeff Garzik
2009-05-09 6:59 ` Ying Chu
2009-05-09 14:38 ` James Bottomley
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=4A045C62.50404@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jasonchu@marvell.com \
--cc=linux-scsi@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