All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Poynor <toddpoynor@google.com>
To: laurence.rochfort@gmail.com
Cc: Rob Springer <rspringer@google.com>,
	benchan@chromium.org, Greg KH <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] staging: gasket: Fix sparse "incorrect type in assignment" warnings.
Date: Mon, 15 Oct 2018 11:42:21 -0700	[thread overview]
Message-ID: <CAAW3YpbLUSicJS788rMTnBJTiKHJy_hW-EOS7s05+V-09zTbrQ@mail.gmail.com> (raw)
In-Reply-To: <20181010212426.3167-1-laurence.rochfort@gmail.com>

On Wed, Oct 10, 2018 at 2:14 PM Laurence Rochfort
<laurence.rochfort@gmail.com> wrote:
>
> Remove the coherent buffer __iomem cookie because the buffer is
> allocated from dma_alloc_coherent().
>
> warning: incorrect type in assignment (different address spaces)
>    expected unsigned char [noderef] [usertype] <asn:2>*virt_base
>    got void *[assigned] mem
> warning: incorrect type in argument 3 (different address spaces)
>    expected void *cpu_addr
>    got unsigned char [noderef] [usertype] <asn:2>*virt_base
>
> Signed-off-by: Laurence Rochfort <laurence.rochfort@gmail.com>
> ---
> Changes in v3:
>  - Just remove the __iommem cookie, don't alter type.
>
>  drivers/staging/gasket/gasket_core.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gasket/gasket_core.h b/drivers/staging/gasket/gasket_core.h
> index 275fd0b..e62adcd 100644
> --- a/drivers/staging/gasket/gasket_core.h
> +++ b/drivers/staging/gasket/gasket_core.h
> @@ -231,7 +231,7 @@ struct gasket_coherent_buffer_desc {
>  /* Coherent buffer structure. */
>  struct gasket_coherent_buffer {
>         /* Virtual base address. */
> -       u8 __iomem *virt_base;
> +       u8 *virt_base;
>
>         /* Physical base address. */
>         ulong phys_base;
> --
> 2.9.5

Reviewed-by: Todd Poynor <toddpoynor@google.com>

Thanks!

      reply	other threads:[~2018-10-15 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 17:52 [PATCH] staging: gasket: Fix sparse "incorrect type in assignment" warnings Laurence Rochfort
2018-10-09 13:13 ` Greg Kroah-Hartman
2018-10-10 14:03   ` Laurence Rochfort
2018-10-10 14:25     ` Greg Kroah-Hartman
2018-10-10 21:24       ` [PATCH v3] " Laurence Rochfort
2018-10-15 18:42         ` Todd Poynor [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=CAAW3YpbLUSicJS788rMTnBJTiKHJy_hW-EOS7s05+V-09zTbrQ@mail.gmail.com \
    --to=toddpoynor@google.com \
    --cc=benchan@chromium.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurence.rochfort@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rspringer@google.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.