From: Andrew Morton <akpm@linux-foundation.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [PATCH] MAINTAINERS: Add Alexandre Belloni as an RTC maintainer
Date: Wed, 25 Mar 2015 15:12:40 -0700 [thread overview]
Message-ID: <20150325151240.562e6fc6f43cceb51ab6c180@linux-foundation.org> (raw)
In-Reply-To: <1427320651-21356-1-git-send-email-alexandre.belloni@free-electrons.com>
On Wed, 25 Mar 2015 22:57:31 +0100 Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
> Add myself as an RTC subsystem maintainer.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> Hi,
>
> I've noticed that most of the patches for the RTC subsystem are currently either
> taken directly by Andrew or going through another maintainer's tree, quite often
> without an Acked-by or Reviewed-by tag.
> I'd like to propose myself as the RTC susbsystem co-maintainer, to mainly help
> Alessandro reviewing incoming patches and maintain a subsystem tree to avoid
> having the RTC patches going through trees when they have no particular
> dependencies.
>
Please start with
http://ozlabs.org/~akpm/mmots/broken-out/rtc-restore-alarm-after-resume.patch
;)
http://lkml.iu.edu/hypermail/linux/kernel/1412.2/03132.html
http://lkml.iu.edu/hypermail/linux/kernel/1501.0/01592.html
http://lkml.iu.edu/hypermail/linux/kernel/1501.0/01614.html
next prev parent reply other threads:[~2015-03-25 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 21:57 Alexandre Belloni
2015-03-25 22:12 ` Andrew Morton [this message]
2015-03-25 22:58 ` Alessandro Zummo
2015-03-28 21:29 ` [rtc-linux] " Alexandre Belloni
2015-03-28 23:28 ` Alessandro Zummo
2015-04-21 18:06 ` Alexandre Belloni
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=20150325151240.562e6fc6f43cceb51ab6c180@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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®