All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
Date: Sun, 22 Mar 2009 02:04:36 +0530	[thread overview]
Message-ID: <1237667676.17548.3.camel@localhost.localdomain> (raw)

Hello Sam, Ingo:

On latest -tip I am getting following warnings:

  LD      arch/x86/pci/built-in.o
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
make[1]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
  CC      arch/x86/power/cpu_64.o
  LD      arch/x86/power/built-in.o
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
make[1]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
  CC      net/socket.o
make[2]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
make[2]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
  CC      net/core/sock.o

[jaswinder@hpdv5 linux-2.6-tip]$ ls -l include/config/auto.conf
-rw-rw-r-- 1 jaswinder jaswinder 18788 2009-03-22 07:14 include/config/auto.conf

[jaswinder@hpdv5 linux-2.6-tip]$ date
Sun Mar 22 02:02:44 IST 2009
[jaswinder@hpdv5 linux-2.6-tip]$ 

Thanks,
--
JSR


             reply	other threads:[~2009-03-21 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21 20:34 Jaswinder Singh Rajput [this message]
2009-03-22  6:03 ` Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future Jaswinder Singh Rajput
2009-03-22  6:20   ` Jaswinder Singh Rajput
2009-03-22 19:06 ` Sam Ravnborg
2009-03-22 19:28   ` Jaswinder Singh Rajput

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=1237667676.17548.3.camel@localhost.localdomain \
    --to=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.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 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.