From: Viresh Kumar <viresh.kumar@linaro.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Javi Merino <javi.merino@arm.com>
Cc: edubezval@gmail.com, linaro-kernel@lists.linaro.org,
amit.daniel@samsung.com, linux-pm@vger.kernel.org,
rui.zhang@intel.com, Amit Daniel Kachhap <amit.kachhap@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
"David S. Miller" <davem@davemloft.net>,
Greg KH <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Joe Perches <joe@perches.com>,
open list <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [PATCH V3] thermal: cpu_cooling: Add MAINTAINERS entry
Date: Thu, 20 Aug 2015 08:40:39 +0530 [thread overview]
Message-ID: <20150820031039.GJ14544@linux> (raw)
In-Reply-To: <55D542F1.3070004@linaro.org>
On 20-08-15, 05:01, Daniel Lezcano wrote:
> On 08/20/2015 04:40 AM, Viresh Kumar wrote:
> >None of the patches are reaching Viresh or Daniel directly as
> >get_maintainers doesn't report us as maintainers. Looks like file header
> >or history of commits isn't able to do that properly.
> >
> >Add a separate entry for cpu_cooling driver in MAINTAINERS.
> >
> >Acked-by: Eduardo Valentin <edubezval@gmail.com>
> >Acked-by: Amit Daniel Kachhap <amit.daniel@samsung.com>
> >Acked-by: Amit Daniel Kachhap <amit.kachhap@gmail.com>
> >Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Shouldn't be Javi Merino in Cc ?
Added him now, he wasn't there as get_maintainers missed his work :)
--
viresh
next prev parent reply other threads:[~2015-08-20 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 2:40 [PATCH V3] thermal: cpu_cooling: Add MAINTAINERS entry Viresh Kumar
2015-08-20 2:40 ` Viresh Kumar
2015-08-20 3:01 ` Daniel Lezcano
2015-08-20 3:10 ` Viresh Kumar [this message]
2015-08-20 6:28 ` Javi Merino
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=20150820031039.GJ14544@linux \
--to=viresh.kumar@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=amit.daniel@samsung.com \
--cc=amit.kachhap@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=edubezval@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javi.merino@arm.com \
--cc=joe@perches.com \
--cc=jslaby@suse.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.