From: Yuantian Tang <Yuantian.Tang@freescale.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"Jason.Jin@freescale.com" <Jason.Jin@freescale.com>
Subject: RE: [PATCH 2/2] cpufreq: qoriq: rename the driver
Date: Fri, 21 Nov 2014 09:16:23 +0000 [thread overview]
Message-ID: <dedc11e3150d44ee89bb1e96b5447687@DM2PR03MB574.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAKohpo=xLOxXrCJNO0LmrVxMDNsFy2Kxg6bNzHm=vQCJnBvSaw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1961 bytes --]
Hello Viresh,
When I use -C -M options, checkpatch reports error:
[tangyt@titan linux-pm]$ ./scripts/checkpatch.pl 0002-cpufreq-qoriq-rename-the-driver.patch
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#15:
drivers/cpufreq/{ppc-corenet-cpufreq.c => qoriq-cpufreq.c} | 0
ERROR: Does not appear to be a unified-diff format patch
total: 1 errors, 1 warnings, 0 lines checked
0002-cpufreq-qoriq-rename-the-driver.patch has style problems, please review.
I just rename it and do not change anyting. Isn't that allowed?
Thanks,
Yuantian
> -----Original Message-----
> From: Viresh Kumar [mailto:viresh.kumar@linaro.org]
> Sent: Friday, November 21, 2014 3:56 PM
> To: Tang Yuantian-B29983
> Cc: Rafael J. Wysocki; Linux Kernel Mailing List; linux-pm@vger.kernel.org;
> linuxppc-dev@ozlabs.org; Jin Zhengxiong-R64188
> Subject: Re: [PATCH 2/2] cpufreq: qoriq: rename the driver
>
> On 21 November 2014 12:58, Tang Yuantian <Yuantian.Tang@freescale.com>
> wrote:
> > This driver works on all QorIQ platforms which include ARM-based cores
> > and PPC-based cores.
> > Rename it in order to represent better.
> >
> > Signed-off-by: Tang Yuantian <Yuantian.Tang@freescale.com>
> > ---
> > drivers/cpufreq/ppc-corenet-cpufreq.c | 371 ----------------------------------
> > drivers/cpufreq/qoriq-cpufreq.c | 371
> ++++++++++++++++++++++++++++++++++
> > 2 files changed, 371 insertions(+), 371 deletions(-) delete mode
> > 100644 drivers/cpufreq/ppc-corenet-cpufreq.c
> > create mode 100644 drivers/cpufreq/qoriq-cpufreq.c
>
> This is not reviewable at all.. How do I verify that you haven't changed something
> in the files as well ?
>
> To make life easy always create patches with:
>
> git format-patch -C -M
>
> Above options handle renames pretty well.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-11-21 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 7:28 [PATCH v2 1/2] cpufreq: qoriq: Make the driver usable on all QorIQ platforms Tang Yuantian
2014-11-21 7:28 ` [PATCH 2/2] cpufreq: qoriq: rename the driver Tang Yuantian
2014-11-21 7:56 ` Viresh Kumar
2014-11-21 9:16 ` Yuantian Tang [this message]
2014-11-21 9:17 ` Viresh Kumar
2014-11-21 7:54 ` [PATCH v2 1/2] cpufreq: qoriq: Make the driver usable on all QorIQ platforms 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=dedc11e3150d44ee89bb1e96b5447687@DM2PR03MB574.namprd03.prod.outlook.com \
--to=yuantian.tang@freescale.com \
--cc=Jason.Jin@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@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
all inboxes | Powered by JetHome®