From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robherring2@gmail.com>, Joe Perches <joe@perches.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Stephen Boyd <sboyd@codeaurora.org>, Nishanth Menon <nm@ti.com>,
Abhilash Kesavan <kesavan.abhilash@gmail.com>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Kevin Hilman <khilman@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Viswanath Puttagunta <viswanath.puttagunta@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Mark Brown <broonie@kernel.org>,
Sudeep Holla <Sudeep.Holla@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH V3 02/16] PM / OPP: Create a directory for opp bindings
Date: Thu, 30 Jul 2015 22:22:40 +0530 [thread overview]
Message-ID: <20150730165240.GF17794@linux> (raw)
In-Reply-To: <CAL_JsqLeBcaaJ05AtW+tyD5Uxuo5uVYLrq3_oKzrv94xhNpZGg@mail.gmail.com>
On 30-07-15, 11:24, Rob Herring wrote:
> On Thu, Jul 30, 2015 at 8:49 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > On 30-07-15, 08:18, Rob Herring wrote:
> >> On Wed, Jul 29, 2015 at 5:52 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >> > More platform specific extended opp bindings will follow and it would be
> >> > easy to manage them with a directory for opp. Lets create that and move
> >> > the existing opp bindings into it.
> >> >
> >> > Cc: Rob Herring <rob.herring@linaro.org>
> >>
> >> Use get_maintainers.pl please so you send to right people and right email.
> >
> > Already done, you were just cc'd as an extra guy :)
>
> No, because no one that is a maintainer of
> Documentation/devicetree/bindings is cc'ed here. You did on the other
> patch, but not here as neither Ian, Mark, Kumar nor Pawel are cc'ed.
No. I sent all of them together and get_maintainers is invoked for all
of them. I checked again and its a bug with get_maintainers.
@Joe: Can you please take a look at that?
Problem description: Because my patch only had this:
-----------8<-------------
---
Documentation/devicetree/bindings/{power => opp}/opp.txt | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/devicetree/bindings/{power => opp}/opp.txt (100%)
diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt
similarity index 100%
rename from Documentation/devicetree/bindings/power/opp.txt
rename to Documentation/devicetree/bindings/opp/opp.txt
------------>8------------
get_maintainers reports this for the patch:
scripts/get_maintainer.pl: file
'0001-PM-OPP-Create-a-directory-for-opp-bindings.patch' doesn't appear
to be a patch. Add -f to options?
> > Cc: Rob Herring <rob.herring@linaro.org>
>
> Still wrong...
Let me send the patch as reply to this one, with personally cc'ing all
people you want me to.
--
viresh
next prev parent reply other threads:[~2015-07-30 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1438166099.git.viresh.kumar@linaro.org>
2015-07-29 10:52 ` [PATCH V3 01/16] PM / OPP: Update bindings to make opp-hz a 64 bit value Viresh Kumar
[not found] ` <f87ca786bca8abce6261dbd79a34218550355684.1438166099.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-30 13:23 ` Rob Herring
2015-07-29 10:52 ` [PATCH V3 02/16] PM / OPP: Create a directory for opp bindings Viresh Kumar
2015-07-30 13:18 ` Rob Herring
2015-07-30 13:49 ` Viresh Kumar
2015-07-30 16:24 ` Rob Herring
2015-07-30 16:52 ` Viresh Kumar [this message]
2015-07-30 16:57 ` [PATCH V3 resend] " Viresh Kumar
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=20150730165240.GF17794@linux \
--to=viresh.kumar@linaro.org \
--cc=Sudeep.Holla@arm.com \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joe@perches.com \
--cc=kesavan.abhilash@gmail.com \
--cc=khilman@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sboyd@codeaurora.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=viswanath.puttagunta@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).