All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: tip tree build warning
Date: Mon, 16 Nov 2009 16:25:03 +1100	[thread overview]
Message-ID: <20091116162503.7f083c3a.sfr@canb.auug.org.au> (raw)

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

Hi all,

Today's linux-next build (x86_64 allmodconfig) produced this warning:

arch/x86/kernel/apic/apic.c: In function 'calibrate_APIC_clock':
arch/x86/kernel/apic/apic.c:650: warning: format '%ld' expects type 'long int', but argument 2 has type 'u32'

Introduced by commit 23af368e9a904f59256c27d371ce223d6cee0430
("clockevents: Use u32 for mult and shift factors").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2009-11-16  5:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  5:25 Stephen Rothwell [this message]
2009-11-16  7:01 ` linux-next: tip tree build failure (Was: linux-next: tip tree build warning) Stephen Rothwell
2009-11-16 10:57   ` [tip:timers/core] sparc: fix printk for change of variable type tip-bot for Stephen Rothwell
2009-11-16 17:05 ` linux-next: tip tree build warning Randy Dunlap
2009-11-23 18:05   ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2010-02-01  7:22 Stephen Rothwell
2010-02-01  7:12 Stephen Rothwell
2009-12-30 23:45 Stephen Rothwell
2009-12-11  4:38 Stephen Rothwell
2009-11-25 10:53 Stephen Rothwell
2009-11-25 12:28 ` Frederic Weisbecker
2009-10-28  7:14 Stephen Rothwell
2009-10-28  7:31 ` Ingo Molnar
2009-10-28  7:41   ` Stephen Rothwell
2009-10-28  7:48     ` Stephen Rothwell
2009-10-28  7:50       ` Ingo Molnar
2009-11-08 13:16         ` Cyrill Gorcunov
2009-11-08 13:32           ` Ingo Molnar
2009-11-08 13:43             ` Cyrill Gorcunov
2009-11-08 18:42             ` Cyrill Gorcunov
2009-11-08 23:39           ` Stephen Rothwell
2009-11-08 21:30         ` Cyrill Gorcunov
2009-11-09  8:10           ` Ingo Molnar
2009-10-13  3:42 Stephen Rothwell
2009-09-11  8:56 Stephen Rothwell
2009-09-13 20:20 ` Geert Uytterhoeven
2009-08-04  6:16 Stephen Rothwell
2009-08-04 16:24 ` Steven Rostedt

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=20091116162503.7f083c3a.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.