From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932087AbcF3U7W (ORCPT ); Thu, 30 Jun 2016 16:59:22 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:35663 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752858AbcF3U7T (ORCPT ); Thu, 30 Jun 2016 16:59:19 -0400 Date: Thu, 30 Jun 2016 22:00:10 +0100 From: Lee Jones To: Joe Perches Cc: SF Markus Elfring , LKML , kernel-janitors@vger.kernel.org, Julia Lawall Subject: Re: [PATCH] mfd: dm355evm_msp: Refactoring for add_child() Message-ID: <20160630210010.GH1707@dell> References: <05b7db2a-437a-60ac-d289-71d2150e7f5f@users.sourceforge.net> <20160608111442.GB14888@dell> <75c1cc23-3a2d-db78-d0f2-b5934b18e828@users.sourceforge.net> <20160628150725.GL24982@dell> <20160628163146.GG29166@dell> <69e96aa0-f3d9-d70d-c3ec-d39b5e9d9f14@users.sourceforge.net> <1467318883.24287.171.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1467318883.24287.171.camel@perches.com> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Jun 2016, Joe Perches wrote: > On Thu, 2016-06-30 at 22:15 +0200, SF Markus Elfring wrote: > > From: Markus Elfring > > 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@users.sourceforge.net> <5682D228.7070902@users.sourceforge.net> <20160111082922.GB14104@x1> <05b7db2a-437a-60ac-d289-71d2150e7f5f@users.sourceforge.net> <20160608111442.GB14888@dell> <75c1cc23-3a2d-db78-d0f2-b5934b18e828@users.sourceforge.net> <20160628150725.GL24982@dell> <20160628163146.GG29166@dell> > In-reply-to: <20160628163146.GG29166@dell>  > > 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