[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140923010418.GI7960@sirena.org.uk>
Date: Mon, 22 Sep 2014 18:04:18 -0700
From: Mark Brown <broonie@...nel.org>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Ben Dooks <ben-linux@...ff.org>,
Kukjin Kim <kgene.kim@...sung.com>,
Sangbeom Kim <sbkim73@...sung.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
Arnd Bergmann <arnd@...db.de>,
Tomasz Figa <tomasz.figa@...il.com>,
linux-samsung-soc@...r.kernel.org, alsa-devel@...a-project.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: samsung: Remove goni or aquila with the WM8994
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]:
> > On Thu, Sep 18, 2014 at 11:43:29AM +0200, Paul Bolle wrote:
> > > Done on top of next-20140918. Untested.
> > > --------->8---------
> > > From: Paul Bolle <pebolle@...cali.nl>
> > 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.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists