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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121119064543.GB21890@avionic-0098.mockup.avionic-design.de>
Date:	Mon, 19 Nov 2012 07:45:43 +0100
From:	Thierry Reding <thierry.reding@...onic-design.de>
To:	Mark Zhang <markz@...dia.com>
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 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.

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

Content of type "application/pgp-signature" skipped