public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new toolchain snapshots
Date: Thu, 31 Aug 2000 07:12:42 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205424@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205422@msgid-missing>

On Wed, 30 Aug 2000 16:54:29 -0700, 
Jim Wilson <wilson@cygnus.com> wrote:
>I am making available new toolchain snapshots, based on July FSF gcc sources.
>These snapshots are available from ftp.cygnus.com in pub/ia64-linux.  The
>current snapshot is in the snap-000828 directory.

I'm getting a lot of warnings for format %p with the new toolchain on
kernel 2.4.0-test7, e.g.

pci-dma.c:100: warning: void format, char arg (arg 2)

static char *io_tlb_start, *io_tlb_end;
        printk("Placing software IO TLB between 0x%p - 0x%p\n", io_tlb_start, io_tlb_end);

What is the correct way to handle these?  Cast all pointers to (void *)
for printing or is there a compiler option I can use to make %p accept
any pointer, i.e. the old behaviour?



  reply	other threads:[~2000-08-31  7:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30 23:54 [Linux-ia64] new toolchain snapshots Jim Wilson
2000-08-31  7:12 ` Keith Owens [this message]
2000-08-31 12:44 ` Dan Pop
2000-08-31 17:43 ` David Mosberger
2000-08-31 20:08 ` Jim Wilson
2000-08-31 20:23 ` David Mosberger
2000-08-31 22:19 ` Jim Wilson
2000-08-31 22:29 ` David Mosberger
2000-09-01  4:49 ` Keith Owens
2000-09-02  3:01 ` Jim Wilson
2000-09-02  4:00 ` Keith Owens

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-105590678205424@msgid-missing \
    --to=kaos@ocs.com.au \
    --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