From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
Rob Herring <rob.herring@calxeda.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/4] ASoc: kirkwood: simplify probe error
Date: Sat, 3 Aug 2013 17:10:29 +0100 [thread overview]
Message-ID: <20130803161029.GD23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130803175513.7b765b0d@armhf>
On Sat, Aug 03, 2013 at 05:55:13PM +0200, Jean-Francois Moine wrote:
> On Sat, 3 Aug 2013 13:39:54 +0100
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>
> > This doesn't apply to mainline as there's a clk_put() there.
>
> Right, it applies to linux-next:
>
> On Fri, 26 Jul 2013 11:32:50 +0100, Mark Brown <broonie@kernel.org> wrote:
>
> > Always submit against where the code will be applied - -next in this
> > case.
Sorry, I'm just not going to bother with your patches unless you start
posting them in such a way that interested parties can test them without
having to run around and pull random trees. In other words, you should
have Cc'd interested parties on that devm_* change patch - especially
myself as I was the one who introduced that code.
next prev parent reply other threads:[~2013-08-03 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 6:17 [PATCH v3 1/4] ASoc: kirkwood: simplify probe error Jean-Francois Moine
2013-08-03 12:39 ` Russell King - ARM Linux
2013-08-03 15:55 ` Jean-Francois Moine
2013-08-03 16:10 ` Russell King - ARM Linux [this message]
2013-08-03 16:31 ` Mark Brown
2013-08-03 12:46 ` Russell King - ARM Linux
2013-08-03 16:52 ` Jean-Francois Moine
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=20130803161029.GD23006@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=perex@perex.cz \
--cc=rob.herring@calxeda.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).