From: Joe Perches <joe@perches.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: Add Daniel as maintainer for drivers/clocksource
Date: Wed, 10 Jul 2013 11:50:11 -0700 [thread overview]
Message-ID: <1373482211.14604.62.camel@joe-AO722> (raw)
In-Reply-To: <51DDA797.4030200@linaro.org>
On Wed, 2013-07-10 at 19:27 +0100, John Stultz wrote:
> I've been doing a bad job at managing the drivers/clocksource directory,
> so Daniel has been helping with review and patch queuing for the clocksource
> and clockevent drivers, so add him formally to the MAINTAINERS list.
>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: John Stultz <john.stultz@linaro.org>
> ---
> MAINTAINERS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5be702c..460c996 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7014,6 +7014,12 @@ F: include/uapi/linux/timex.h
> F: kernel/time/clocksource.c
> F: kernel/time/time*.c
> F: kernel/time/ntp.c
> +
> +CLOCKSOURCE, CLOCKEVENT DRIVERS
> +M: Daniel Lezcano <daniel.lezcano@linaro.org>
> +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: drivers/clocksource
Sections in alphabetical order please.
Does this even apply?
It looks more like an interdiff.
Should the F: include/linux/clocksource.h
and F: kernel/time/clocksource.c entries
above this be moved too?
next prev parent reply other threads:[~2013-07-10 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 18:27 John Stultz
2013-07-10 18:50 ` Joe Perches [this message]
2013-07-10 18:53 ` John Stultz
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=1373482211.14604.62.camel@joe-AO722 \
--to=joe@perches.com \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--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
all inboxes | Powered by JetHome®