From: Andy Shevchenko <andriy.shevchenko@linux•intel.com>
To: Hans de Goede <hdegoede@redhat•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Mark Gross <mark.gross@intel•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the drivers-x86 tree
Date: Thu, 4 Feb 2021 17:05:47 +0200 [thread overview]
Message-ID: <YBwNS6iO1RhY+2Lf@smile.fi.intel.com> (raw)
In-Reply-To: <5461d70a-39a0-0322-e2ae-6434e0d1e0a3@redhat.com>
On Thu, Feb 04, 2021 at 08:38:40AM +0100, Hans de Goede wrote:
> Hi Stephen, Andy,
>
> On 2/4/21 6:13 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the drivers-x86 tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/platform/x86/intel_scu_wdt.c: In function 'register_mid_wdt':
> > drivers/platform/x86/intel_scu_wdt.c:66:28: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
> > 66 | wdt_dev.dev.platform_data = (const struct intel_mid_wdt_pdata *)id->driver_data;
> > | ^
> >
> > Introduced by commit
> >
> > a507e5d90f3d ("platform/x86: intel_scu_wdt: Get rid of custom x86 model comparison")
>
> Thank you for the bug report.
>
> Andy can you send me a fix for this please ?
Fix just has been sent.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-02-04 16:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 5:13 linux-next: build warning after merge of the drivers-x86 tree Stephen Rothwell
2021-02-04 7:38 ` Hans de Goede
2021-02-04 15:05 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 10:45 Stephen Rothwell
2025-04-30 10:51 ` Antheas Kapenekakis
2025-04-30 10:55 ` Ilpo Järvinen
2025-04-30 11:01 ` Antheas Kapenekakis
2025-04-30 11:07 ` Ilpo Järvinen
2024-08-20 3:43 Stephen Rothwell
2024-08-20 4:31 ` Kuppuswamy Sathyanarayanan
2024-08-23 19:16 ` Joseph, Jithu
2024-07-15 7:03 Stephen Rothwell
2024-01-05 6:29 Stephen Rothwell
2023-02-03 2:53 Stephen Rothwell
2023-02-03 9:25 ` Hans de Goede
2020-02-10 23:35 Stephen Rothwell
2020-02-10 23:39 ` Kammela, Gayatri
2020-02-11 21:07 ` 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=YBwNS6iO1RhY+2Lf@smile.fi.intel.com \
--to=andriy.shevchenko@linux$(echo .)intel.com \
--cc=hdegoede@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mark.gross@intel$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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