linux-kernel - Re: [PATCH V9 RESEND 00/14] Add T210 support in Tegra soctherm

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: <20160329151307.GA1855@localhost.localdomain>
Date:	Tue, 29 Mar 2016 08:13:09 -0700
From:	Eduardo Valentin <edubezval@...il.com>
To:	Wei Ni <wni@...dia.com>
Cc:	rui.zhang@...el.com, thierry.reding@...il.com,
	MLongnecker@...dia.com, swarren@...dotorg.org,
	mikko.perttunen@...si.fi, linux-tegra@...r.kernel.org,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V9 RESEND 00/14] Add T210 support in Tegra soctherm

On Tue, Mar 29, 2016 at 06:36:48PM +0800, Wei Ni wrote:
> Hi Eduardo,
> I resent this V9 series in one mail thread.

I personally prefer in one mail thread, like
you did here. But It is fine for me if you send either way,
in one mail thread or each patch in its own thread. 

What I found strange is that in your v8 patches from 1 to 4 have the
message id of patch 0 in its in-reply-to field (one email thread). But
patches 5 to 14 don't (each patch in a single thread). Which made me
wonder if this is a bug in git send email of if you intentionally did
that, for some reason.

BTW, now the patch series applies fine.

BR,

Eduardo Valentin