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]
Date:	Thu, 28 Jul 2016 14:58:04 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Jan Glauber <jan.glauber@...iumnetworks.com>
Cc:	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
	David Daney <david.daney@...ium.com>,
	"Steven J . Hill" <steven.hill@...ium.com>
Subject: Re: [PATCH v2] spi: octeon: Add thunderx driver

On Thu, Jul 28, 2016 at 10:12:55AM +0200, Jan Glauber wrote:
> On Wed, Jul 27, 2016 at 07:08:24PM +0100, Mark Brown wrote:

> > Don't send individual patches in reply to the middle of threads, it
> > makes it really confusing what's going on.  I now have multiple patches

> With multiple being exactly two. I thought it to be easier this way
> around and the ordering to be obvious (if you use threading),
> but of course I can resend the two patches as a new series.

The threading wasn't even visible in my inbox since I delete mails after
I'm done with them, the only reason I knew you were replying in the
middle of a series was that I still had David's mail to reply to.  Even
if the threading is visible it gets very confusing if you've got a
series consisting of different versions of patches at different levels
of the thread, it's not always going to be direct replacements of
individual patches.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ