mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hannes Eder" <hannes@hanneseder.net>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Karsten Keil" <kkeil@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 9/9] mISDN: fix sparse warnings
Date: Thu, 11 Dec 2008 14:41:34 +0100	[thread overview]
Message-ID: <154e089b0812110541x26534df0k47b320f54759df8e@mail.gmail.com> (raw)
In-Reply-To: <87hc5cc60n.fsf@basil.nowhere.org>

On Wed, Dec 10, 2008 at 6:08 PM, Andi Kleen <andi@firstfloor.org> wrote:
> Hannes Eder <hannes@hanneseder.net> writes:
>> @@ -918,7 +919,7 @@ hfcmulti_resync(struct hfc_multi *locked, struct hfc_multi *newmaster, int rm)
>>       /* Disable sync of all cards */
>>       list_for_each_entry_safe(hc, next, &HFClist, list) {
>>               if (test_bit(HFC_CHIP_PLXSD, &hc->chip)) {
>> -                     plx_acc_32 = (u_int *)(hc->plx_membase+PLX_GPIOC);
>> +                     plx_acc_32 = (u_int __iomem *)(hc->plx_membase+PLX_GPIOC);
>
> It would be probably better to declare plx_membase __iomem too instead
> of so much casting.

it is, but of type "u_char __iomem *" (after applying this patch):

+       u_char __iomem  *pci_membase; /* PCI memory (MUST BE BYTE POINTER) */

so thats why we need the cast.

What if we declare plx_acc_32 of type "u_char __iomem *", or both as
"void __iomem *"?
I slightly favor the later, against the LOUD comment.

If plx_membase is declared without __iomem the cast "(u_int __iomem*)" produces
a warning "cast adds address space to expression"

-Hannes

      reply	other threads:[~2008-12-11 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 15:43 Hannes Eder
2008-12-10 17:08 ` Andi Kleen
2008-12-11 13:41   ` Hannes Eder [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=154e089b0812110541x26534df0k47b320f54759df8e@mail.gmail.com \
    --to=hannes@hanneseder.net \
    --cc=andi@firstfloor.org \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®