From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 0/4] Pending S3C64xx updates
Date: Fri, 27 Jan 2012 11:27:51 +0000 [thread overview]
Message-ID: <20120127112751.GF32008@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <016501ccdc93$ae158190$0a4084b0$%kim@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
On Fri, Jan 27, 2012 at 10:33:24AM +0900, Kukjin Kim wrote:
> Mark Brown wrote:
> > ARM: S3C64XX: Define some additional always off clocks
> Hmm, I know there were discussions about this with Tomasz Figa and I was
> waiting for his submitting. But now this looks ok to me so will apply this.
The discussion there was around there being other out of tree drivers
that might at some point want to use these clocks - I don't think there
was any doubt that for current mainline this change makes sense.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Pending S3C64xx updates
Date: Fri, 27 Jan 2012 11:27:51 +0000 [thread overview]
Message-ID: <20120127112751.GF32008@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <016501ccdc93$ae158190$0a4084b0$%kim@samsung.com>
On Fri, Jan 27, 2012 at 10:33:24AM +0900, Kukjin Kim wrote:
> Mark Brown wrote:
> > ARM: S3C64XX: Define some additional always off clocks
> Hmm, I know there were discussions about this with Tomasz Figa and I was
> waiting for his submitting. But now this looks ok to me so will apply this.
The discussion there was around there being other out of tree drivers
that might at some point want to use these clocks - I don't think there
was any doubt that for current mainline this change makes sense.
-------------- 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/20120127/c826a4b5/attachment.sig>
next prev parent reply other threads:[~2012-01-27 11:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 21:31 [PATCH 0/4] Pending S3C64xx updates Mark Brown
2012-01-24 21:31 ` Mark Brown
2012-01-24 21:31 ` [PATCH 1/4] ARM: S3C64XX: Make s3c64xx_init_uarts() static Mark Brown
2012-01-24 21:31 ` Mark Brown
2012-01-24 21:31 ` [PATCH 2/4] ARM: S3C64XX: Define some additional always off clocks Mark Brown
2012-01-24 21:31 ` Mark Brown
2012-01-24 21:31 ` [PATCH 3/4] ARM: S3C6410: Use device names for both I2C clocks Mark Brown
2012-01-24 21:31 ` Mark Brown
2012-01-24 21:31 ` [PATCH 4/4] ARM: S3C64XX: Add hookup for Tomatin module on Cragganmore Mark Brown
2012-01-24 21:31 ` Mark Brown
2012-01-27 1:33 ` [PATCH 0/4] Pending S3C64xx updates Kukjin Kim
2012-01-27 1:33 ` Kukjin Kim
2012-01-27 11:27 ` Mark Brown [this message]
2012-01-27 11:27 ` Mark Brown
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=20120127112751.GF32008@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
/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.