From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Anton Vasilyev <vasilyev@ispras.ru>
Subject: Re: [PATCH] firmware: vpd: Drop __iomem usage for memremap() memory
Date: Mon, 18 Mar 2019 11:36:36 -0700 [thread overview]
Message-ID: <20190318183636.GA31345@roeck-us.net> (raw)
In-Reply-To: <20190318155457.197339-1-swboyd@chromium.org>
On Mon, Mar 18, 2019 at 08:54:57AM -0700, Stephen Boyd wrote:
> memremap() doesn't return an iomem pointer, so we can just use memcpy()
> and drop the __iomem annotation here. This silences a sparse warning.
>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Anton Vasilyev <vasilyev@ispras.ru>
> Smgned-off-by: Stephen Boyd <swboyd@chromium.org>
Smgned ?
Other than that,
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/firmware/google/vpd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/google/vpd.c b/drivers/firmware/google/vpd.c
> index c0c0b4e4e281..f240946ed701 100644
> --- a/drivers/firmware/google/vpd.c
> +++ b/drivers/firmware/google/vpd.c
> @@ -254,7 +254,7 @@ static int vpd_section_destroy(struct vpd_section *sec)
>
> static int vpd_sections_init(phys_addr_t physaddr)
> {
> - struct vpd_cbmem __iomem *temp;
> + struct vpd_cbmem *temp;
> struct vpd_cbmem header;
> int ret = 0;
>
> @@ -262,7 +262,7 @@ static int vpd_sections_init(phys_addr_t physaddr)
> if (!temp)
> return -ENOMEM;
>
> - memcpy_fromio(&header, temp, sizeof(struct vpd_cbmem));
> + memcpy(&header, temp, sizeof(struct vpd_cbmem));
> memunmap(temp);
>
> if (header.magic != VPD_CBMEM_MAGIC)
> --
> Sent by a computer through tubes
>
next prev parent reply other threads:[~2019-03-18 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:54 Stephen Boyd
2019-03-18 18:36 ` Guenter Roeck [this message]
2019-03-18 19:38 ` Stephen Boyd
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=20190318183636.GA31345@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.org \
--cc=vasilyev@ispras.ru \
/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®