From: Mark Zhang <markz@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "airlied@redhat.com" <airlied@redhat.com>,
"thierry.reding@avionic-design.de"
<thierry.reding@avionic-design.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] drm: Add NVIDIA Tegra30 support
Date: Mon, 19 Nov 2012 14:18:51 +0800 [thread overview]
Message-ID: <50A9CF4B.2040308@nvidia.com> (raw)
In-Reply-To: <50A66A02.6030608@wwwdotorg.org>
On 11/17/2012 12:29 AM, Stephen Warren wrote:
> On 11/15/2012 09:58 PM, Mark Zhang wrote:
>> This patch is based on Thierry's drm patch for Tegra20:
>> - [PATCH v2 0/6] Device tree updates for host1x support
>> - [PATCH v3 0/2] NVIDIA Tegra DRM driver
>>
>> It adds the support for NVIDIA Tegra30.
>
> Mark, I tried to apply this for testing locally, but it doesn't apply.
>
> For some reason, all the whitespace in the context has been replaced
> with spaces. Are your local copies of dc.c and host1x.c indented with
> spaces for some reason, or did the MS Exchange server corrupt your patch
> as you sent it (I've previously only observed inbound corruption...)
>
I think that is because the whitespace in patch which Thierry sent:
"[PATCH v3 1/2] drm: Add NVIDIA Tegra20 support" are all spaces, not tabs.
P.S: I saved the patch mail into an eml file and use "git am <eml file>"
to integrate it into my local tree.
next prev parent reply other threads:[~2012-11-19 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 4:58 [PATCH] drm: Add NVIDIA Tegra30 support Mark Zhang
2012-11-16 6:43 ` Thierry Reding
2012-11-16 6:48 ` Mark Zhang
2012-11-16 7:11 ` Thierry Reding
2012-11-16 7:15 ` Mark Zhang
2012-11-16 16:29 ` Stephen Warren
2012-11-19 6:18 ` Mark Zhang [this message]
2012-11-19 6:45 ` Thierry Reding
2012-11-19 7:17 ` Mark Zhang
2012-11-16 16:43 ` 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=50A9CF4B.2040308@nvidia.com \
--to=markz@nvidia.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@avionic-design.de \
/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;
as well as URLs for NNTP newsgroup(s).