public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add the generic sched_clock under timekeeping
Date: Wed, 17 Jul 2013 12:21:12 -0700	[thread overview]
Message-ID: <51E6EEA8.7040504@linaro.org> (raw)
In-Reply-To: <20130717191222.GW6950@tarshish>

On 07/17/2013 12:12 PM, Baruch Siach wrote:
> Hi John,
>
> On Wed, Jul 17, 2013 at 11:57:32AM -0700, John Stultz wrote:
>> On 07/17/2013 03:05 AM, Baruch Siach wrote:
>>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>>> ---
>>>   MAINTAINERS | 2 ++
>>>   1 file changed, 2 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index bf61e04..bd9616a 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -7129,6 +7129,7 @@ M:	Thomas Gleixner <tglx@linutronix.de>
>>>   T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
>>>   S:	Supported
>>>   F:	include/linux/clocksource.h
>>> +F:	include/linux/sched_clock.h
>>>   F:	include/linux/time.h
>>>   F:	include/linux/timex.h
>>>   F:	include/uapi/linux/time.h
>>> @@ -7136,6 +7137,7 @@ F:	include/uapi/linux/timex.h
>>>   F:	kernel/time/clocksource.c
>>>   F:	kernel/time/time*.c
>>>   F:	kernel/time/ntp.c
>>> +F:	kernel/time/sched_clock.c
>> It seems like we could probably simplify this bit to kernel/time/*, no?
> This would add jiffies.c and all the tick-* files that are currently covered
> by the "HIGH-RESOLUTION TIMERS, CLOCKEVENTS, DYNTICKS" section.

Ok, fair enough. My thought was it all goes through Thomas anyway, but 
for those sections there are different combinations of folks who 
co-maintain.

thanks
-john


  parent reply	other threads:[~2013-07-17 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 10:05 [PATCH] MAINTAINERS: add the generic sched_clock under timekeeping Baruch Siach
2013-07-17 18:57 ` John Stultz
2013-07-17 19:12   ` Baruch Siach
2013-07-17 19:18     ` Joe Perches
2013-07-17 19:21     ` John Stultz [this message]
2013-08-19  3:28       ` Baruch Siach

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=51E6EEA8.7040504@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=baruch@tkos.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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