linux-kernel - Re: [PATCH] drm: Add NVIDIA Tegra30 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <50A9DCFC.3050005@nvidia.com>
Date:	Mon, 19 Nov 2012 15:17:16 +0800
From:	Mark Zhang <markz@...dia.com>
To:	Thierry Reding <thierry.reding@...onic-design.de>
CC:	Stephen Warren <swarren@...dotorg.org>,
	"airlied@...hat.com" <airlied@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH] drm: Add NVIDIA Tegra30 support

On 11/19/2012 02:45 PM, Thierry Reding wrote:
> * PGP Signed by an unknown key
> 
> On Mon, Nov 19, 2012 at 02:18:51PM +0800, Mark Zhang wrote:
>> 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.
> 
> I'm pretty sure the issue must be inbound corruption caused by you email
> setup. The patches I've sent use tabs properly and I've never seen my
> setup corrupt emails.
> 

Sorry Thierry. It's my bad. I tried to apply Alex's patch and found it
has the same issue, the whitespace is filled with spaces...

I also found if the patch is for dts files, the whitespaces are tabs.
That is really weird.

> It seems like this is not the first time that this happens for you guys
> and I think I remember it to be the reason why Stephen switched to using
> his private email address for open-source work. Your IT guys should fix
> this, really. It can't be that hard.
> 
> Thierry
> 
> * Unknown Key
> * 0x7F3EB3A1
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/