From: John Stultz <john.stultz@linaro.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [time:fortglx/3.7/time 11/13] include/linux/timekeeper_internal.h:101:1: sparse: missing identif
Date: Sat, 22 Sep 2012 00:47:38 +0000 [thread overview]
Message-ID: <505D0AAA.3070907@linaro.org> (raw)
In-Reply-To: <20120922004111.GH5959@localhost>
On 09/21/2012 05:41 PM, Fengguang Wu wrote:
> Hi John,
>
> FYI, there are new sparse warnings show up in
>
> tree: git://git.linaro.org/people/jstultz/linux.git fortglx/3.7/time
> head: f9bb3ff13c4701ee6242ec4b4ef0cbc71d5ff299
> commit: 672364f56055976aae7e68b59cf578173a3dbddc [11/13] time: Introduce new GENERIC_TIME_VSYSCALL
>
> All sparse warnings:
>
[snip]
> 98 #else
> 99
> 100 static inline void update_vsyscall(struct timekeeper *tk);
> > 101 {
> 102 }
> 103 static inline void update_vsyscall_tz(void)
> 104 {
> 105 }
> 106 #endif
> 107
> 108 #endif /* _LINUX_TIMEKEEPER_INTERNAL_H */
>
I just caught this myself and have re-pushed out a fix to that tree.
Thanks again for the automated testing!
-john
prev parent reply other threads:[~2012-09-22 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 0:41 [time:fortglx/3.7/time 11/13] include/linux/timekeeper_internal.h:101:1: sparse: missing identifier Fengguang Wu
2012-09-22 0:47 ` John Stultz [this message]
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=505D0AAA.3070907@linaro.org \
--to=john.stultz@linaro.org \
--cc=kernel-janitors@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