From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Mike Rapoport <mike.rapoport-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c-mux-reg: fix compilation warnings
Date: Thu, 3 Sep 2015 11:57:18 +0200 [thread overview]
Message-ID: <20150903095718.GB720@katana> (raw)
In-Reply-To: <1441181021-4937-1-git-send-email-mike.rapoport-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Wed, Sep 02, 2015 at 11:03:41AM +0300, Mike Rapoport wrote:
> With CONFIG_OF=n, the following warnings occur when compiling
> drivers/i2c/muxes/i2c-mux-reg.c:
>
> CC drivers/i2c/muxes/i2c-mux-reg.o
> drivers/i2c/muxes/i2c-mux-reg.c:170:13: warning: ‘struct gpiomux’ declared inside parameter list [enabled by default]
> struct platform_device *pdev)
> ^
> drivers/i2c/muxes/i2c-mux-reg.c:170:13: warning: its scope
> is only this definition or declaration, which is probably not what you want [enabled by default]
> drivers/i2c/muxes/i2c-mux-reg.c: In function ‘i2c_mux_reg_probe’:
> drivers/i2c/muxes/i2c-mux-reg.c:201:3: warning: passing argument 1 of ‘i2c_mux_reg_probe_dt’ from incompatible pointer type [enabled by default]
> ret = i2c_mux_reg_probe_dt(mux, pdev);
> ^
>
> Signed-off-by: Mike Rapoport <mike.rapoport-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Applied to for-next, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-09-03 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 8:03 [PATCH] i2c-mux-reg: fix compilation warnings Mike Rapoport
[not found] ` <1441181021-4937-1-git-send-email-mike.rapoport-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-03 9:57 ` Wolfram Sang [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=20150903095718.GB720@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mike.rapoport-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).