From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752942AbaIXU1e (ORCPT ); Wed, 24 Sep 2014 16:27:34 -0400 Received: from cpsmtpb-ews07.kpnxchange.com ([213.75.39.10]:63470 "EHLO cpsmtpb-ews07.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752501AbaIXU1b (ORCPT ); Wed, 24 Sep 2014 16:27:31 -0400 Message-ID: <1411590448.19525.42.camel@x220> Subject: Re: [PATCH] ASoC: samsung: Remove goni or aquila with the WM8994 From: Paul Bolle To: Mark Brown Cc: Ben Dooks , Kukjin Kim , Sangbeom Kim , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Arnd Bergmann , Tomasz Figa , linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Date: Wed, 24 Sep 2014 22:27:28 +0200 In-Reply-To: <20140923010418.GI7960@sirena.org.uk> References: <1404496099-26708-1-git-send-email-t.figa@samsung.com> <53C675E4.4020502@samsung.com> <1409825105.5546.91.camel@x220> <201409041802.36466.arnd@arndb.de> <1411033409.2017.15.camel@x220> <20140918175752.GC7960@sirena.org.uk> <1411077427.2012.6.camel@x41> <20140923010418.GI7960@sirena.org.uk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-3.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Sep 2014 20:27:29.0025 (UTC) FILETIME=[F6119F10:01CFD835] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2014-09-22 at 18:04 -0700, Mark Brown wrote: > On Thu, Sep 18, 2014 at 11:57:07PM +0200, Paul Bolle wrote: > > Mark Brown schreef op do 18-09-2014 om 10:57 [-0700]: > > > Please follow the patch submission process in SubmittingPatches. > > > Could you please be more specific? What part of SubmittingPatches have I > > skipped? > > > Is it the perhaps the use of scissors? Or the superfluous From: line? > > "git am -c" appears to handle this message (and the very similar message > > I also sent today) just fine. > > It's the fact that you've included the patch in the middle of the reply > to another mail in the middle of a thread after some other stuff; you > can tell this isn't the normal process by observing that your mail > doesn't look visually close to a normal patch submission - if that's the > case then people aren't likely to sit around and try to figure out some > magic set of git options needed, manually edit or otherwise special case > to special case it unless it's *really* important. I see. I hope to resend shortly. Thanks! Paul Bolle From mboxrd@z Thu Jan 1 00:00:00 1970 From: pebolle@tiscali.nl (Paul Bolle) Date: Wed, 24 Sep 2014 22:27:28 +0200 Subject: [PATCH] ASoC: samsung: Remove goni or aquila with the WM8994 In-Reply-To: <20140923010418.GI7960@sirena.org.uk> References: <1404496099-26708-1-git-send-email-t.figa@samsung.com> <53C675E4.4020502@samsung.com> <1409825105.5546.91.camel@x220> <201409041802.36466.arnd@arndb.de> <1411033409.2017.15.camel@x220> <20140918175752.GC7960@sirena.org.uk> <1411077427.2012.6.camel@x41> <20140923010418.GI7960@sirena.org.uk> Message-ID: <1411590448.19525.42.camel@x220> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, 2014-09-22 at 18:04 -0700, Mark Brown wrote: > On Thu, Sep 18, 2014 at 11:57:07PM +0200, Paul Bolle wrote: > > Mark Brown schreef op do 18-09-2014 om 10:57 [-0700]: > > > Please follow the patch submission process in SubmittingPatches. > > > Could you please be more specific? What part of SubmittingPatches have I > > skipped? > > > Is it the perhaps the use of scissors? Or the superfluous From: line? > > "git am -c" appears to handle this message (and the very similar message > > I also sent today) just fine. > > It's the fact that you've included the patch in the middle of the reply > to another mail in the middle of a thread after some other stuff; you > can tell this isn't the normal process by observing that your mail > doesn't look visually close to a normal patch submission - if that's the > case then people aren't likely to sit around and try to figure out some > magic set of git options needed, manually edit or otherwise special case > to special case it unless it's *really* important. I see. I hope to resend shortly. Thanks! Paul Bolle