From: Alexey Perevalov <a.perevalov@samsung.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, john.stultz@linaro.org,
anton@nomsg.org, kyungmin.park@samsung.com,
cw00.choi@samsung.com, akpm@linux-foundation.org
Subject: Re: [PATCH v3 1/6] tracing/trivial: Add CLOCK_BOOTIME and CLOCK_TAI for human readable clockid trace
Date: Thu, 20 Feb 2014 20:25:50 +0400 [thread overview]
Message-ID: <53062C8E.30301@samsung.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402201158170.4468@ionos.tec.linutronix.de>
On 02/20/2014 03:01 PM, Thomas Gleixner wrote:
>
> On Thu, 20 Feb 2014, Alexey Perevalov wrote:
>
>> These clockids is also used in current hrtimer implementation.
>>
>> Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
>> ---
>> include/trace/events/timer.h | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/trace/events/timer.h b/include/trace/events/timer.h
>> index 185b2c6..547b79f 100644
>> --- a/include/trace/events/timer.h
>> +++ b/include/trace/events/timer.h
>> @@ -11,7 +11,10 @@
>> #define clockid_to_string(clockid) \
>> __print_symbolic(clockid, \
>> { CLOCK_MONOTONIC, "CLOCK_MONOTONIC" }, \
>> - { CLOCK_REALTIME, "CLOCK_REALTIME" })
>> + { CLOCK_REALTIME, "CLOCK_REALTIME" }, \
>> + { CLOCK_BOOTTIME, "CLOCK_BOOTTIME" }, \
>> + { CLOCK_TAI, "CLOCK_TAI" } \
>> + )
> patching file include/trace/events/timer.h
> Hunk #1 FAILED at 11.
> 1 out of 1 hunk FAILED -- rejects in file include/trace/events/timer.h
>
> Brilliant stuff this.
>
>
>
>
>
Sorry, I missed one patch
--
Best regards,
Alexey Perevalov
next prev parent reply other threads:[~2014-02-20 16:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 8:40 [PATCH v3 0/6] Deferrable timers support for hrtimers/timerfd API Alexey Perevalov
2014-02-20 8:40 ` [PATCH v3 1/6] tracing/trivial: Add CLOCK_BOOTIME and CLOCK_TAI for human readable clockid trace Alexey Perevalov
2014-02-20 11:01 ` Thomas Gleixner
2014-02-20 16:25 ` Alexey Perevalov [this message]
2014-02-20 8:40 ` [PATCH v3 2/6] hrtimer: Add support for deferrable timer into the hrtimer Alexey Perevalov
2014-02-20 18:49 ` John Stultz
2014-02-20 21:18 ` Thomas Gleixner
2014-02-20 21:20 ` John Stultz
2014-02-20 21:56 ` Thomas Gleixner
2014-02-20 8:40 ` [PATCH v3 3/6] kernel/time: Add new helpers to convert ktime to/from jiffies Alexey Perevalov
2014-02-20 10:34 ` Thomas Gleixner
2014-02-20 8:40 ` [PATCH v3 4/6] timerfd: Factor out timer-type unspecific timerfd_expire() Alexey Perevalov
2014-02-20 10:52 ` Thomas Gleixner
2014-02-20 16:30 ` Alexey Perevalov
2014-02-21 4:13 ` Anton Vorontsov
2014-02-21 7:04 ` Alexey Perevalov
2014-02-21 10:41 ` Thomas Gleixner
2014-02-20 8:40 ` [PATCH v3 5/6] timerfd: Add support for deferrable timers Alexey Perevalov
2014-02-20 11:09 ` Thomas Gleixner
2014-02-21 4:11 ` Anton Vorontsov
2014-02-21 10:40 ` Thomas Gleixner
2014-02-20 8:40 ` [PATCH v3 6/6] tracing/trivial: Add CLOCK_*_DEFERRABLE for tracing clockids Alexey Perevalov
2014-02-20 11:12 ` [PATCH v3 0/6] Deferrable timers support for hrtimers/timerfd API Thomas Gleixner
2014-02-20 16:53 ` Alexey Perevalov
2014-02-20 21:21 ` Thomas Gleixner
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=53062C8E.30301@samsung.com \
--to=a.perevalov@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=anton@nomsg.org \
--cc=cw00.choi@samsung.com \
--cc=john.stultz@linaro.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox