From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joe Perches <joe@perches.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound: max98090: Remove executable bit
Date: Thu, 21 Mar 2013 22:26:24 +0100 [thread overview]
Message-ID: <20130321212623.GK15926@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1363898422.30275.47.camel@joe-AO722>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Thu, Mar 21, 2013 at 01:40:22PM -0700, Joe Perches wrote:
> On Thu, 2013-03-21 at 21:37 +0100, Mark Brown wrote:
> > you routinely send very trivial
> > patches which don't apply cleanly
> That's demonstrably false.
It's sadly not, at least for the things I get to see - as far as I have
been able to tell you submit against either Linus' tree or the last
release (I think the former) rather than the relevant development trees
or even -next which means that if anyone else has looked at the same
area of code there will be conflicts.
> I'm done with this conversation.
Oh, well. Hopefully you'll take on board the feedback.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-03-21 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 21:58 [PATCH] sound: max98090: Remove executable bit Joe Perches
2013-03-20 9:57 ` Mark Brown
2013-03-20 15:22 ` Joe Perches
2013-03-20 16:36 ` Mark Brown
2013-03-20 22:54 ` Joe Perches
2013-03-21 16:25 ` Mark Brown
2013-03-21 17:16 ` Joe Perches
2013-03-21 17:44 ` Mark Brown
2013-03-21 17:44 ` Mark Brown
2013-03-21 17:53 ` Joe Perches
2013-03-21 18:44 ` Mark Brown
2013-03-21 18:44 ` Mark Brown
2013-03-21 19:16 ` Joe Perches
2013-03-21 19:16 ` Joe Perches
2013-03-21 20:37 ` Mark Brown
2013-03-21 20:40 ` Joe Perches
2013-03-21 21:26 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130321212623.GK15926@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=joe@perches.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.