linux-kernel - Re: [PATCH] mfd: dm355evm_msp: Refactoring for add

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: <20160630210010.GH1707@dell>
Date:	Thu, 30 Jun 2016 22:00:10 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Joe Perches <joe@...ches.com>
Cc:	SF Markus Elfring <elfring@...rs.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>,
	kernel-janitors@...r.kernel.org,
	Julia Lawall <julia.lawall@...6.fr>
Subject: Re: [PATCH] mfd: dm355evm_msp: Refactoring for add_child()

On Thu, 30 Jun 2016, Joe Perches wrote:

> On Thu, 2016-06-30 at 22:15 +0200, SF Markus Elfring wrote:
> > From: Markus Elfring <elfring@...rs.sourceforge.net>
> > Date: Thu, 30 Jun 2016 21:54:51 +0200
> > 
> > Adjust jump targets according to the Linux coding style convention.
> > Another check for the variable "status" can be omitted then at the
> > end.
> 
> Two headers in this email:
> 
> References: <566ABCD9.1060404@...rs.sourceforge.net> <5682D228.7070902@...rs.sourceforge.net> <20160111082922.GB14104@x1> <05b7db2a-437a-60ac-d289-71d2150e7f5f@...rs.sourceforge.net> <de3598c4-f85a-6807-303a-55ee0ac707f2@...rs.sourceforge.net> <20160608111442.GB14888@...l> <e4eaf0b4-e539-b400-c8a2-70f210cee1fa@...rs.sourceforge.net> <75c1cc23-3a2d-db78-d0f2-b5934b18e828@...rs.sourceforge.net> <20160628150725.GL24982@...l> <c220895b-e56f-dc95-500d-0cf9d2f51777@...rs.sourceforge.net> <20160628163146.GG29166@...l>
> In-reply-to: <20160628163146.GG29166@...l> 
> 
> Can you please fix your email client to _not_ send References:
> and In-reply-to: headers when sending new patches?  Thanks.
> 
> Even better would be to use git send-email for these patches.

Yes, I've mentioned this before.

I now have a gargantuan threaded mess consisting of 53 mails in my
inbox.  Please submit patches using `git send-email`, not forgetting
to increase your submission each time you submit i.e [PATCH v2] and
send them independently i.e. not attached to previous submissions.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog