linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the pm tree
Date: Thu, 15 Oct 2020 18:20:47 +1100	[thread overview]
Message-ID: <20201015182047.28c739da@canb.auug.org.au> (raw)
In-Reply-To: <20201008203559.735dd600@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2742 bytes --]

Hi all,

On Thu, 8 Oct 2020 20:35:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> On Thu, 1 Oct 2020 19:43:37 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Tue, 22 Sep 2020 18:11:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:  
> > >
> > > After merging the pm tree, today's linux-next build (i386 defconfig)
> > > produced this warning:
> > > 
> > > In file included from include/acpi/acpi.h:24,
> > >                  from drivers/acpi/acpica/hwgpe.c:10:
> > > drivers/acpi/acpica/hwgpe.c: In function 'acpi_hw_gpe_read':
> > > include/acpi/actypes.h:501:48: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> > >   501 | #define ACPI_CAST_PTR(t, p)             ((t *) (acpi_uintptr_t) (p))
> > >       |                                                ^
> > > drivers/acpi/acpica/acmacros.h:18:41: note: in expansion of macro 'ACPI_CAST_PTR'
> > >    18 | #define ACPI_CAST8(ptr)                 ACPI_CAST_PTR (u8, (ptr))
> > >       |                                         ^~~~~~~~~~~~~
> > > drivers/acpi/acpica/acmacros.h:22:43: note: in expansion of macro 'ACPI_CAST8'
> > >    22 | #define ACPI_GET8(ptr)                  (*ACPI_CAST8 (ptr))
> > >       |                                           ^~~~~~~~~~
> > > drivers/acpi/acpica/hwgpe.c:50:17: note: in expansion of macro 'ACPI_GET8'
> > >    50 |   *value = (u64)ACPI_GET8(reg->address);
> > >       |                 ^~~~~~~~~
> > > drivers/acpi/acpica/hwgpe.c: In function 'acpi_hw_gpe_write':
> > > include/acpi/actypes.h:501:48: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> > >   501 | #define ACPI_CAST_PTR(t, p)             ((t *) (acpi_uintptr_t) (p))
> > >       |                                                ^
> > > drivers/acpi/acpica/acmacros.h:18:41: note: in expansion of macro 'ACPI_CAST_PTR'
> > >    18 | #define ACPI_CAST8(ptr)                 ACPI_CAST_PTR (u8, (ptr))
> > >       |                                         ^~~~~~~~~~~~~
> > > drivers/acpi/acpica/acmacros.h:26:43: note: in expansion of macro 'ACPI_CAST8'
> > >    26 | #define ACPI_SET8(ptr, val)             (*ACPI_CAST8 (ptr) = (u8) (val))
> > >       |                                           ^~~~~~~~~~
> > > drivers/acpi/acpica/hwgpe.c:85:3: note: in expansion of macro 'ACPI_SET8'
> > >    85 |   ACPI_SET8(reg->address, value);
> > >       |   ^~~~~~~~~
> > > 
> > > Introduced by commit
> > > 
> > >   7a8379eb41a4 ("ACPICA: Add support for using logical addresses of GPE blocks")    
> > 
> > I am still getting these warnings ...  
> 
> Still there :-(

This is now in Linus' tree :-(

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-10-15  7:20 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  8:11 linux-next: build warning after merge of the pm tree Stephen Rothwell
2020-10-01  9:43 ` Stephen Rothwell
2020-10-08  9:35   ` Stephen Rothwell
2020-10-15  7:20     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-05  5:00 Stephen Rothwell
2024-02-05  5:30 ` Meng, Li (Jassmine)
2022-02-06 22:40 Stephen Rothwell
2021-10-13  6:28 Stephen Rothwell
2022-01-17 22:02 ` Stephen Rothwell
2021-03-31  0:29 Stephen Rothwell
2021-03-31  6:22 ` Vitaly Kuznetsov
2021-04-02 17:18   ` Rafael J. Wysocki
2021-02-15  0:39 Stephen Rothwell
2021-02-15 10:23 ` Andy Shevchenko
2021-02-15 10:24   ` Andy Shevchenko
2021-02-22  8:34 ` Stephen Rothwell
2021-01-27  1:43 Stephen Rothwell
2021-01-27  3:54 ` Zhang Rui
2020-11-19  0:09 Stephen Rothwell
2020-11-19 16:22 ` Andy Shevchenko
2020-07-30  2:55 Stephen Rothwell
2020-07-30  3:10 ` Neal Liu
2020-01-19 23:40 Stephen Rothwell
2019-10-14 23:08 Stephen Rothwell
2019-10-15  8:23 ` Andy Shevchenko
2019-10-15  9:41   ` Rafael J. Wysocki
     [not found] <201907111346291954773@zte.com.cn>
2019-07-11 12:26 ` Rafael J. Wysocki
2019-07-11  1:31 Stephen Rothwell
2019-01-23 23:45 Stephen Rothwell
2018-07-30  2:00 Stephen Rothwell
2018-07-30  7:24 ` Sakari Ailus
2018-07-30  7:30   ` jacopo mondi
2018-07-31  0:39   ` Stephen Rothwell
2018-06-08  0:30 Stephen Rothwell
2018-06-08  9:14 ` Rafael J. Wysocki
2018-04-09  1:24 Stephen Rothwell
2018-04-10  7:05 ` Rafael J. Wysocki
2016-11-13 23:40 Stephen Rothwell
2016-11-14  0:03 ` Rafael J. Wysocki
2016-11-14  8:49   ` Akshay Adiga
2014-11-17  2:44 Stephen Rothwell
2014-11-17 11:31 ` Paul Bolle
2014-11-17 23:14   ` Rafael J. Wysocki
2014-11-17 23:45     ` Paul Bolle
2014-11-18  0:34       ` Rafael J. Wysocki
2014-10-29  2:51 Stephen Rothwell
2014-10-29 14:55 ` Rafael J. Wysocki
2014-10-29 15:23   ` Fengguang Wu
2014-10-29 15:56     ` Rafael J. Wysocki

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=20201015182047.28c739da@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).