All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Darren Hart <dvhart@infradead.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Gayatri Kammela <gayatri.kammela@intel.com>
Subject: Re: linux-next: build warning after merge of the drivers-x86 tree
Date: Tue, 11 Feb 2020 23:07:21 +0200	[thread overview]
Message-ID: <CAHp75Vf6p4Sf3hcNV-q_pfDYvgDVodPykgn98mumcj13BGN+Vg@mail.gmail.com> (raw)
In-Reply-To: <20200211103530.41d1e6ed@canb.auug.org.au>

On Tue, Feb 11, 2020 at 1:35 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/platform/x86/intel_pmc_core.c: In function 'pmc_core_resume':
> drivers/platform/x86/intel_pmc_core.c:1329:43: warning: passing argument 4 of 'pmc_core_lpm_display' makes integer from pointer without a cast [-Wint-conversion]
>  1329 |   pmc_core_lpm_display(pmcdev, dev, NULL, "STATUS", offset, maps);
>       |                                           ^~~~~~~~
>       |                                           |
>       |                                           char *
> drivers/platform/x86/intel_pmc_core.c:978:30: note: expected 'u32' {aka 'unsigned int'} but argument is of type 'char *'
>   978 |      struct seq_file *s, u32 offset,
>       |                          ~~~~^~~~~~
> drivers/platform/x86/intel_pmc_core.c:1329:53: warning: passing argument 5 of 'pmc_core_lpm_display' makes pointer from integer without a cast [-Wint-conversion]
>  1329 |   pmc_core_lpm_display(pmcdev, dev, NULL, "STATUS", offset, maps);
>       |                                                     ^~~~~~
>       |                                                     |
>       |                                                     int
> drivers/platform/x86/intel_pmc_core.c:979:18: note: expected 'const char *' but argument is of type 'int'
>   979 |      const char *str,
>       |      ~~~~~~~~~~~~^~~
>
> Introduced by commit
>
>   2cf128fbf321 ("platform/x86: intel_pmc_core: Dump low power status registers on an S0ix.y failure")

Thank you, Stephen,
Fix had been incorporated.


-- 
With Best Regards,
Andy Shevchenko

  parent reply	other threads:[~2020-02-11 21:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 23:35 linux-next: build warning after merge of the drivers-x86 tree Stephen Rothwell
2020-02-10 23:39 ` Kammela, Gayatri
2020-02-11 21:07 ` Andy Shevchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05  6:29 Stephen Rothwell
2023-02-03  2:53 Stephen Rothwell
2023-02-03  9:25 ` Hans de Goede
2021-02-04  5:13 Stephen Rothwell
2021-02-04  7:38 ` Hans de Goede
2021-02-04 15:05   ` Andy Shevchenko
2020-01-10  3:57 Stephen Rothwell
2020-01-10  9:47 ` Andy Shevchenko
2017-06-30  4:00 Stephen Rothwell
2017-06-30  5:12 ` Arvind Yadav
2017-07-01  3:32 ` Darren Hart
2017-05-19  3:23 Stephen Rothwell
2017-05-19 22:09 ` Darren Hart
2017-05-22 18:03   ` Andy Shevchenko
2017-05-25 23:34     ` Stephen Rothwell
2017-05-26  8:25       ` Arnd Bergmann
2017-05-26  8:35         ` Stephen Rothwell
2017-05-26  9:04           ` Andy Shevchenko
2017-05-26  9:07             ` Stephen Rothwell
2017-05-26  9:52               ` Andy Shevchenko
2016-12-14  2:50 Stephen Rothwell
2016-12-14 22:21 ` Darren Hart
2016-12-14 22:59   ` Darren Hart
2016-12-15  0:02     ` Stephen Rothwell
2016-12-15  4:07       ` Darren Hart
2010-08-27  1:59 Stephen Rothwell
2010-08-27  2:51 ` Matthew Garrett
2010-08-27  7:40   ` Dmitry Torokhov
2010-08-30  2:51     ` Stephen Rothwell
2010-06-25  3:25 Stephen Rothwell
2010-06-25  3:31 ` Matthew Garrett
2010-06-25  3:41 ` Matthew Garrett
2010-06-25  4:16   ` Stephen Rothwell

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=CAHp75Vf6p4Sf3hcNV-q_pfDYvgDVodPykgn98mumcj13BGN+Vg@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=gayatri.kammela@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.