From: Danny Huang <dahuang@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Joseph Lo <josephl@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Hiroshi Doyu <hdoyu@nvidia.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: tegra114: add speedo-based process identification
Date: Wed, 20 Mar 2013 09:42:51 +0800 [thread overview]
Message-ID: <1363743771.3573.55.camel@dahuang-vm> (raw)
In-Reply-To: <5148A645.9020009@wwwdotorg.org>
On Wed, 2013-03-20 at 01:54 +0800, Stephen Warren wrote:
> On 03/18/2013 05:17 AM, Danny Huang wrote:
> > Add speedo-based process identifictaion for Tegra114.
>
> I have applied this to Tegra's for-3.10/soc branch, with one addition below:
>
> > diff --git a/arch/arm/mach-tegra/tegra114_speedo.c b/arch/arm/mach-tegra/tegra114_speedo.c
>
> > +#include <linux/kernel.h>
>
> Here, I also added:
>
> #include <linux/bug.h>
>
> That's not needed in the Tegra for-next branch (which is based on
> 3.9-rc1), but is needed when merged into linux-next, and hence will
> presumably be needed once this is submitted into 3.10.
Thanks. Does it mean that we have to include the bug.h for all newly
created file for 3.10?
next prev parent reply other threads:[~2013-03-20 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 11:17 Danny Huang
2013-03-19 17:54 ` Stephen Warren
2013-03-20 1:42 ` Danny Huang [this message]
2013-03-20 1:49 ` Stephen Warren
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=1363743771.3573.55.camel@dahuang-vm \
--to=dahuang@nvidia.com \
--cc=hdoyu@nvidia.com \
--cc=josephl@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pgaikwad@nvidia.com \
--cc=swarren@wwwdotorg.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®