From: Mark Brown <broonie@kernel.org>
To: boris brezillon <b.brezillon@overkiz.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/5] ASoC: atmel-ssc: remove clk_disable_unprepare call from critical section
Date: Thu, 18 Jul 2013 11:58:46 +0100 [thread overview]
Message-ID: <20130718105846.GJ22506@sirena.org.uk> (raw)
In-Reply-To: <51E7C1B2.8000206@overkiz.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On Thu, Jul 18, 2013 at 12:21:38PM +0200, boris brezillon wrote:
> I can send you the whole series if you want (already sent to LKML
> and LAKML).
> But I'd like to understand who I should send patches from this series to.
When you send me patch 5/5 with no other information on the rest of the
series I've no idea if there's any dependencies on the other code or
anything like that. The key thing here is to make sure the people
getting the patch can understand the interdependencies somehow.
If you're sending a bunch of unrelated changes with no dependencies
you're better off sending them all separately rather than as a part of a
series.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 5/5] ASoC: atmel-ssc: remove clk_disable_unprepare call from critical section
Date: Thu, 18 Jul 2013 11:58:46 +0100 [thread overview]
Message-ID: <20130718105846.GJ22506@sirena.org.uk> (raw)
In-Reply-To: <51E7C1B2.8000206@overkiz.com>
On Thu, Jul 18, 2013 at 12:21:38PM +0200, boris brezillon wrote:
> I can send you the whole series if you want (already sent to LKML
> and LAKML).
> But I'd like to understand who I should send patches from this series to.
When you send me patch 5/5 with no other information on the rest of the
series I've no idea if there's any dependencies on the other code or
anything like that. The key thing here is to make sure the people
getting the patch can understand the interdependencies somehow.
If you're sending a bunch of unrelated changes with no dependencies
you're better off sending them all separately rather than as a part of a
series.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130718/d69af9e4/attachment.sig>
next prev parent reply other threads:[~2013-07-18 10:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 7:32 [PATCH v4 0/5] ARM: at91: prepare transition to common clk framework Boris BREZILLON
2013-07-18 7:32 ` Boris BREZILLON
2013-07-18 7:34 ` [PATCH v4 1/5] ARM: at91/tc/clocksource: replace clk_enable/disable with clk_prepare_enable/disable_unprepare Boris BREZILLON
2013-07-18 7:34 ` Boris BREZILLON
2013-07-18 7:38 ` [PATCH v4 2/5] mmc: atmel-mci: prepare clk before calling enable Boris BREZILLON
2013-07-18 7:38 ` Boris BREZILLON
2013-08-22 9:41 ` boris brezillon
2013-08-22 9:41 ` boris brezillon
2013-08-25 3:18 ` Chris Ball
2013-08-25 3:18 ` Chris Ball
2013-08-25 5:35 ` boris brezillon
2013-08-25 5:35 ` boris brezillon
2013-07-18 7:40 ` [PATCH v4 3/5] at91/avr32/atmel_lcdfb: " Boris BREZILLON
2013-07-18 7:40 ` Boris BREZILLON
2013-07-18 7:40 ` Boris BREZILLON
2013-08-30 7:18 ` Tomi Valkeinen
2013-08-30 7:18 ` Tomi Valkeinen
2013-08-30 7:18 ` Tomi Valkeinen
2013-07-18 7:43 ` [PATCH v4 4/5] USB: gadget: atmel_usba: " Boris BREZILLON
2013-07-18 7:43 ` Boris BREZILLON
2013-07-18 7:48 ` [PATCH v4 5/5] ASoC: atmel-ssc: remove clk_disable_unprepare call from critical section Boris BREZILLON
2013-07-18 7:48 ` Boris BREZILLON
2013-07-18 9:53 ` Mark Brown
2013-07-18 9:53 ` Mark Brown
2013-07-18 10:21 ` boris brezillon
2013-07-18 10:21 ` boris brezillon
2013-07-18 10:58 ` Mark Brown [this message]
2013-07-18 10:58 ` Mark Brown
2013-07-18 11:33 ` boris brezillon
2013-07-18 11:33 ` boris brezillon
2013-07-18 11:25 ` Mark Brown
2013-07-18 11:25 ` Mark Brown
2013-07-18 11:34 ` boris brezillon
2013-07-18 11:34 ` boris brezillon
2013-07-18 7:58 ` [PATCH v4 1/5] ARM: at91/tc/clocksource: replace clk_enable/disable with clk_prepare_enable/disable_unprepare Boris BREZILLON
2013-07-18 7:58 ` Boris BREZILLON
2013-08-21 12:13 ` Nicolas Ferre
2013-08-21 12:13 ` Nicolas Ferre
2013-07-22 17:03 ` [PATCH v4 0/5] ARM: at91: prepare transition to common clk framework Jean-Christophe PLAGNIOL-VILLARD
2013-07-22 17:03 ` Jean-Christophe PLAGNIOL-VILLARD
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=20130718105846.GJ22506@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=b.brezillon@overkiz.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
/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.