From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 01/11] ARM: shmobile: r7s72100: document MSTP clock support
Date: Tue, 13 May 2014 23:53:35 +0000 [thread overview]
Message-ID: <20140513235335.GF6784@verge.net.au> (raw)
In-Reply-To: <20140513215929.GA3967@katana>
On Tue, May 13, 2014 at 11:59:29PM +0200, Wolfram Sang wrote:
> Simon,
>
> > Its a getting a little to close to rc6 for me to take this series for v3.16,
> > especially considering some bits seem to need tweaking (I am thinking of sci).
> >
> > Could you either:
> >
> > * Re-post it without the sci changes and
> > I'll look at queuing it up for v3.17 or;
>
> If it is possible and does not cause too much burden for you, I'd prefer
> to include it soonish and handle the fixups incrementally. Since it
> touches a few files which change a lot, rebasing and retesting is extra
> work (done twice for this series IIRC) and thus I'd prefer to do the
> clenaups as seperate patches.
>
> So, if no one objects, I'll resend tomorrow with Geerts fixup folded
> into my series and retested against latest renesas/devel.
I will do my best. But I need to have pull-requests sent off
to the arm-soc maintainers before rc6 appears. And ideally patches
should have been present in next for a day before I send such a request.
So by my calculations I need to push things to my next tree very
soon (i.e. today) in order to reach the above mentioned criteria.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 01/11] ARM: shmobile: r7s72100: document MSTP clock support
Date: Wed, 14 May 2014 08:53:35 +0900 [thread overview]
Message-ID: <20140513235335.GF6784@verge.net.au> (raw)
In-Reply-To: <20140513215929.GA3967@katana>
On Tue, May 13, 2014 at 11:59:29PM +0200, Wolfram Sang wrote:
> Simon,
>
> > Its a getting a little to close to rc6 for me to take this series for v3.16,
> > especially considering some bits seem to need tweaking (I am thinking of sci).
> >
> > Could you either:
> >
> > * Re-post it without the sci changes and
> > I'll look at queuing it up for v3.17 or;
>
> If it is possible and does not cause too much burden for you, I'd prefer
> to include it soonish and handle the fixups incrementally. Since it
> touches a few files which change a lot, rebasing and retesting is extra
> work (done twice for this series IIRC) and thus I'd prefer to do the
> clenaups as seperate patches.
>
> So, if no one objects, I'll resend tomorrow with Geerts fixup folded
> into my series and retested against latest renesas/devel.
I will do my best. But I need to have pull-requests sent off
to the arm-soc maintainers before rc6 appears. And ideally patches
should have been present in next for a day before I send such a request.
So by my calculations I need to push things to my next tree very
soon (i.e. today) in order to reach the above mentioned criteria.
next prev parent reply other threads:[~2014-05-13 23:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 10:03 [PATCH v4 00/11] CCF support for Renesas r7s72100 Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 01/11] ARM: shmobile: r7s72100: document MSTP clock support Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-30 1:41 ` Simon Horman
2014-04-30 1:41 ` Simon Horman
2014-04-30 1:41 ` Simon Horman
2014-04-30 18:21 ` Geert Uytterhoeven
2014-04-30 18:21 ` Geert Uytterhoeven
2014-04-30 18:21 ` Geert Uytterhoeven
2014-05-13 0:05 ` Mike Turquette
2014-05-13 0:05 ` Mike Turquette
2014-05-13 1:57 ` Simon Horman
2014-05-13 1:57 ` Simon Horman
2014-05-13 21:59 ` Wolfram Sang
2014-05-13 21:59 ` Wolfram Sang
2014-05-13 23:53 ` Simon Horman [this message]
2014-05-13 23:53 ` Simon Horman
2014-05-14 0:11 ` Wolfram Sang
2014-05-14 0:11 ` Wolfram Sang
2014-05-14 2:50 ` Simon Horman
2014-05-14 2:50 ` Simon Horman
2014-05-14 10:26 ` Geert Uytterhoeven
2014-05-14 10:26 ` Geert Uytterhoeven
2014-05-14 12:21 ` Stephen Rothwell
2014-05-14 12:21 ` Stephen Rothwell
2014-04-29 10:03 ` [PATCH v5 02/11] ARM: shmobile: r7s72100: add essential clock nodes to dtsi Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 03/11] ARM: shmobile: r7s72100: genmai: populate nodes for external clocks Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 04/11] ARM: shmobile: r7s72100: add scif nodes to dtsi Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-30 0:58 ` Laurent Pinchart
2014-04-30 0:58 ` Laurent Pinchart
2014-04-30 1:43 ` Simon Horman
2014-04-30 1:43 ` Simon Horman
2014-04-29 10:03 ` [PATCH v5 05/11] ARM: shmobile: r7s72100: genmai: add uart alias and activate scif2 as console Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 06/11] ARM: shmobile: r7s72100: genmai: platform scif devices only for legacy support Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 07/11] ARM: shmobile: r7s72100: add i2c clocks to dtsi Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 08/11] ARM: shmobile: r7s72100: remove I2C DT clocks from legacy clock support Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 09/11] ARM: shmobile: r7s72100: add spi clocks to dtsi Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 10:03 ` [PATCH v5 10/11] ARM: shmobile: r7s72100: remove SPI DT clocks from legacy clock support Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-30 18:17 ` Geert Uytterhoeven
2014-04-30 18:17 ` Geert Uytterhoeven
2014-04-29 10:03 ` [PATCH v5 11/11] ARM: shmobile: r7s72100: use workaround for non DT-clocks Wolfram Sang
2014-04-29 10:03 ` Wolfram Sang
2014-04-29 13:32 ` [PATCH v4 00/11] CCF support for Renesas r7s72100 Magnus Damm
2014-04-29 13:32 ` Magnus Damm
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=20140513235335.GF6784@verge.net.au \
--to=horms@verge.net.au \
--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 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.