From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Lior Dotan <liodot@gmail.com>
Subject: Re: [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits
Date: Thu, 17 Nov 2016 14:33:02 +0300 [thread overview]
Message-ID: <20161117113302.GU28558@mwanda> (raw)
In-Reply-To: <CAMhs-H_Q=n=x7BhesTa=mpY+k3E8KyNw-mCVfEhaoSERv-e3Gw@mail.gmail.com>
On Thu, Nov 17, 2016 at 12:22:00PM +0100, Sergio Paracuellos wrote:
> On Thu, Nov 17, 2016 at 11:51 AM, Dan Carpenter
> <dan.carpenter@oracle.com> wrote:
> > Hm... I seem to duplicate the Sparse warnings at all. That's weird.
> >
>
> With this patch applied, sparse warnings dissapear for me... That's weird.
>
I understand that.
> > Anyway as far as I can tell the warnings are false positives... Can't
> > you just remove the __iomem tag? Have you tested this change?
> >
> I haven' t tested this change because I can't test it :(. Do you think
> that just removing
> __iomem tag is enough?
Give it a shot and see if the warnings go away. I don't think the tag
is correct.
regards,
dan carpenter
next prev parent reply other threads:[~2016-11-17 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 5:42 [PATCH v3 0/2] staging: slicoss: fix different address space warnings Sergio Paracuellos
2016-11-17 5:42 ` [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits Sergio Paracuellos
2016-11-17 10:51 ` Dan Carpenter
2016-11-17 11:22 ` Sergio Paracuellos
2016-11-17 11:33 ` Dan Carpenter [this message]
2016-11-17 11:46 ` Sergio Paracuellos
2016-11-18 7:45 ` Greg KH
2016-11-17 5:42 ` [PATCH v3 2/2] staging: slicoss: fix different address space warnings: 64 bits Sergio Paracuellos
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=20161117113302.GU28558@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@gmail.com \
--cc=sergio.paracuellos@gmail.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).