public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Integer to Pointer Cast Warnings when Building 2.4.17
Date: Mon, 03 Jun 2002 17:23:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905632@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905629@msgid-missing>

>>>>> On Mon, 3 Jun 2002 17:57:47 +0530, "LAKSHMIPATHY,ARUN (HP-India,ex2)" <arun_lakshmipathy@hp.com> said:

  Arun> make[4]: Entering directory
  Arun> `/kernel/linux/drivers/acpi/dispatcher' dswexec.c: In function
  Arun> `acpi_ds_exec_end_op': dswexec.c:580: warning: cast from
  Arun> pointer to integer of different size

  Arun> make[4]: Entering directory
  Arun> `/kernel/linux/drivers/acpi/events' evevent.c: In function
  Arun> `acpi_ev_asynch_execute_gpe_method': evevent.c:686: warning:
  Arun> cast from pointer to integer of different size evevent.c: In
  Arun> function `acpi_ev_gpe_dispatch': evevent.c:802: warning: cast
  Arun> to pointer from integer of different size

  Arun> make[3]: Entering directory `/kernel/linux/drivers/acpi' os.c:
  Arun> In function `acpi_os_get_root_pointer': os.c:206: warning:
  Arun> assignment makes integer from pointer without a cast

These come from the ACPI subsystem.  They annoy me, too, but it's up
to the ACPI folks to fix them.  It's possible they're already fixed in
the latest ACPI drops.

	--david


  parent reply	other threads:[~2002-06-03 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03 12:39 [Linux-ia64] Integer to Pointer Cast Warnings when Building 2.4.17 LAKSHMIPATHY,ARUN (HP-India,ex2)
2002-06-03 14:48 ` [Linux-ia64] Integer to Pointer Cast Warnings when Building 2 Matt_Domsch
2002-06-03 15:00 ` [Linux-ia64] Integer to Pointer Cast Warnings when Building 2.4.17 n0ano
2002-06-03 17:23 ` David Mosberger [this message]
2002-06-03 17:35 ` Matthew Wilcox

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=marc-linux-ia64-105590701905632@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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