From: Viresh Kumar <viresh.kumar@linaro.org>
To: Cristian Ardelean <cristian97.ardelean@gmail.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: integrator: fixed coding style issues
Date: Mon, 13 Jul 2015 08:01:46 +0530 [thread overview]
Message-ID: <20150713023146.GC10415@linux> (raw)
In-Reply-To: <1436553735-17622-1-git-send-email-cristian97.ardelean@gmail.com>
On 10-07-15, 14:42, Cristian Ardelean wrote:
> Fixed coding style issues found by checkpatch.pl tool. Changed
> space indentation to tab, removed unneccesary braces, removed
> space between MODULE macros and parentheses.
>
> REMARKS: failed to 'make' this file with error message
> 'fatal error: asm/mach-types.h: No such file or directory'.
>
> Signed-off-by: Cristian Ardelean <cristian97.ardelean@gmail.com>
> ---
> drivers/cpufreq/integrator-cpufreq.c | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2015-07-13 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 18:42 [PATCH] cpufreq: integrator: fixed coding style issues Cristian Ardelean
2015-07-13 2:31 ` Viresh Kumar [this message]
2015-07-16 0:33 ` Rafael J. Wysocki
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=20150713023146.GC10415@linux \
--to=viresh.kumar@linaro.org \
--cc=cristian97.ardelean@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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