From: Stephen Warren <swarren@wwwdotorg.org>
To: Bill Huang <bilhuang@nvidia.com>
Cc: rjw@sisk.pl, viresh.kumar@linaro.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] cpufreq: tegra: Remove not used header and clean up codes
Date: Wed, 11 Sep 2013 13:19:28 -0600 [thread overview]
Message-ID: <5230C240.8050602@wwwdotorg.org> (raw)
In-Reply-To: <1378898355-31290-2-git-send-email-bilhuang@nvidia.com>
On 09/11/2013 05:19 AM, Bill Huang wrote:
> Remove inclustion of the not needed header files and remove the logic
> to check the CPU ID to not exceeding the maximum supported CPUs.
> diff --git a/drivers/cpufreq/tegra-cpufreq.c b/drivers/cpufreq/tegra-cpufreq.c
> - * Copyright (C) 2010 Google, Inc.
> + * Copyright (c) 2013, NVIDIA Corporation.
> + * Copyright (C) 2010-2013 Google, Inc.
This is such a trivial patch, I don't think it's appropriate to add an
NVIDIA (c) notice. It may well be appropriate in patch 2/2.
I assume that Google didn't write this patch, so why adjust that (c) notice?
next prev parent reply other threads:[~2013-09-11 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 11:19 [PATCH 0/2] Remodel Tegra cpufreq driver to support Tegra series SoCs Bill Huang
2013-09-11 11:19 ` [PATCH 1/2] cpufreq: tegra: Remove not used header and clean up codes Bill Huang
2013-09-11 19:19 ` Stephen Warren [this message]
2013-09-11 11:19 ` [PATCH 2/2] cpufreq: tegra: Re-model Tegra cpufreq driver Bill Huang
2013-09-11 19:33 ` Stephen Warren
2013-09-12 2:03 ` Bill Huang
2013-09-12 10:14 ` Peter De Schrijver
2013-09-12 10:35 ` Bill Huang
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=5230C240.8050602@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bilhuang@nvidia.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rjw@sisk.pl \
--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