From: Stephen Warren <swarren@nvidia.com>
To: Axel Lin <axel.lin@gmail.com>,
"Grant Likely (grant.likely@secretlab.ca)"
<grant.likely@secretlab.ca>,
"Russell King - ARM Linux (linux@arm.linux.org.uk)"
<linux@arm.linux.org.uk>
Cc: Colin Cross <ccross@android.com>,
Erik Gilling <konkers@android.com>,
Olof Johansson <olof@lixom.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ARM: tegra: Add missing include of linux/erron.h and linux/types.h
Date: Tue, 16 Aug 2011 09:27:05 -0700 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF04AEA25328@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1313471744.5824.2.camel@phoenix>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 917 bytes --]
Axel Lin wrote at Monday, August 15, 2011 11:16 PM:
> Include linux/erron.h to fix below build error.
...
> Include linux/types.h to fix below build error.
...
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> This patch is against linux-next (next-20110815), it fixes the build error with "make
> tegra_defconfig".
Axel,
I posted this same thing a little while back. Russell asked me to perform
some rework on gpio.h that removed the need for errno.h instead. I did
that in:
http://www.spinics.net/lists/linux-tegra/msg01996.html
I'm just waiting for an Ack from Grant Likely on the GPIO driver changes,
and then will place the series into the ARM patch system as Russell
requested.
Thanks for caring about Tegra compile issues:-)
--
nvpublic
ÿôèº{.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¥
prev parent reply other threads:[~2011-08-16 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 5:15 Axel Lin
2011-08-16 5:19 ` Baruch Siach
2011-08-16 16:27 ` Stephen Warren [this message]
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=74CDBE0F657A3D45AFBB94109FB122FF04AEA25328@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=axel.lin@gmail.com \
--cc=ccross@android.com \
--cc=grant.likely@secretlab.ca \
--cc=konkers@android.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=olof@lixom.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
all inboxes | Powered by JetHome®