From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 00/12] CCF support for Renesas r7s72100
Date: Fri, 7 Mar 2014 17:47:41 +0100 [thread overview]
Message-ID: <20140307164741.GJ28943@katana> (raw)
In-Reply-To: <1552759.qGZNIXqrb1@avalon>
> > That would have saved only 2 lines since we need the workaround anyhow
> > (MTU2) and would break the incremental approach of this series somewhat.
> > I'd like to keep it.
>
> It would have saved one patch. If Simon needs to apply CCF support separately
> I'm fine with that approach, but if both changes are applied at the same time
> the SCIF patches could go in first.
Which one would be saved? We need to workaround anyhow (patch 5) and
some scif cleanup besides the workaround is needed, too (patch 7). No?
-------------- 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/20140307/b306629e/attachment-0001.sig>
next prev parent reply other threads:[~2014-03-07 16:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 16:00 [PATCH V3 00/12] CCF support for Renesas r7s72100 Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 01/12] clk: shmobile: add CPG driver for rz-platforms Wolfram Sang
2014-03-21 1:26 ` Mike Turquette
2014-03-07 16:00 ` [PATCH V3 02/12] ARM: shmobile: r7s72100: document MSTP clock support Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 03/12] ARM: shmobile: r7s72100: add essential clock nodes to dtsi Wolfram Sang
2014-03-07 16:22 ` Ben Dooks
2014-03-07 16:33 ` Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 04/12] ARM: shmobile: r7s72100: genmai: populate nodes for external clocks Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 05/12] ARM: shmobile: r7s72100: use workaround for non DT-clocks Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 06/12] ARM: shmobile: r7s72100: add scif nodes to dtsi Wolfram Sang
2014-03-07 16:13 ` Laurent Pinchart
2014-03-07 16:25 ` Wolfram Sang
2014-03-07 16:37 ` Laurent Pinchart
2014-03-07 16:44 ` Wolfram Sang
2014-03-07 16:48 ` Laurent Pinchart
2014-03-07 16:48 ` Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 07/12] ARM: shmobile: r7s72100: genmai: activate scif2 for console output Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 08/12] ARM: shmobile: r7s72100: genmai: platform scif devices only for legacy support Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 09/12] ARM: shmobile: r7s72100: add i2c clocks to dtsi Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 10/12] ARM: shmobile: r7s72100: remove I2C DT clocks from legacy clock support Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 11/12] ARM: shmobile: r7s72100: add spi clocks to dtsi Wolfram Sang
2014-03-07 16:00 ` [PATCH V3 12/12] ARM: shmobile: r7s72100: remove SPI DT clocks from legacy clock support Wolfram Sang
2014-03-07 16:14 ` [PATCH V3 00/12] CCF support for Renesas r7s72100 Laurent Pinchart
2014-03-07 16:29 ` Wolfram Sang
2014-03-07 16:36 ` Laurent Pinchart
2014-03-07 16:47 ` Wolfram Sang [this message]
2014-03-07 16:59 ` Laurent Pinchart
2014-03-10 7:27 ` Wolfram Sang
2014-03-10 11:59 ` Laurent Pinchart
2014-03-27 6:46 ` Wolfram Sang
2014-03-27 10:56 ` Laurent Pinchart
2014-03-27 11:36 ` Wolfram Sang
2014-03-27 12:50 ` Laurent Pinchart
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=20140307164741.GJ28943@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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 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).