From: Thierry Reding <thierry.reding@gmail.com>
To: Jan Moskyto Matejka <mq@suse.cz>
Cc: Alan Cox <alan@linux.intel.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [linux-next] pwm: lpss: fix const qualifier discard warning
Date: Wed, 7 May 2014 10:41:38 +0200 [thread overview]
Message-ID: <20140507084137.GD6362@ulmo> (raw)
In-Reply-To: <1399044179-17912-1-git-send-email-mq@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Fri, May 02, 2014 at 05:22:59PM +0200, Jan Moskyto Matejka wrote:
> Fixing this warning:
> drivers/pwm/pwm-lpss.c: In function ‘pwm_lpss_probe_pci’:
> drivers/pwm/pwm-lpss.c:192:2: warning: passing argument 3 of ‘pwm_lpss_probe’ discards ‘const’ qualifier from pointer target type [enabled by default]
> lpwm = pwm_lpss_probe(&pdev->dev, &pdev->resource[0], info);
> ^
> drivers/pwm/pwm-lpss.c:130:30: note: expected ‘struct pwm_lpss_boardinfo *’ but argument is of type ‘const struct pwm_lpss_boardinfo *’
> static struct pwm_lpss_chip *pwm_lpss_probe(struct device *dev,
>
> That warning was introduced in commit 093e00bb3f82f3c67e2d1682e316fc012bcd0d92
> ("pwm: lpss: Add support for PCI devices").
>
> Signed-off-by: Jan Moskyto Matejka <mq@suse.cz>
> ---
> drivers/pwm/pwm-lpss.c | 1 +
> 1 file changed, 1 insertion(+)
This was reported over a week ago by the kbuild test robot and I've had
fixes for this (and an additional sparse warning) in my tree for a while
now. Interestingly everybody at Intel seems to have forgotten about this
driver after their patches got merged since nobody cared to respond.
I've now pushed out the patch that I had locally.
Thanks,
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-07 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:22 [PATCH] [linux-next] pwm: lpss: fix const qualifier discard warning Jan Moskyto Matejka
2014-05-07 8:41 ` Thierry Reding [this message]
2014-05-07 9:48 ` Alan Cox
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=20140507084137.GD6362@ulmo \
--to=thierry.reding@gmail.com \
--cc=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mq@suse.cz \
/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.