linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Fixes for v4.6
Date: Wed, 20 Apr 2016 08:54:48 +1000	[thread overview]
Message-ID: <20160419225448.GD9826@verge.net.au> (raw)
In-Reply-To: <1461057123.8777.31.camel@collabora.co.uk>

On Tue, Apr 19, 2016 at 11:12:03AM +0200, Sjoerd Simons wrote:
> Hey Simon,
> On Mon, 2016-04-18 at 14:12 +1000, Simon Horman wrote:
> > Hi Geert, Hi Sjoerd,
> > 
> > On Tue, Apr 12, 2016 at 08:02:54AM +0900, Simon Horman wrote:
> > > 
> > > On Mon, Apr 11, 2016 at 09:11:19AM +0200, Geert Uytterhoeven wrote:
> > > > 
> > > > Hi Simon,
> > > > 
> > > > On Mon, Apr 11, 2016 at 3:52 AM, Simon Horman
> > > > <horms+renesas@verge.net.au> wrote:
> > > > > 
> > > > > Hi Olof, Hi Kevin, Hi Arnd,
> > > > > 
> > > > > Please consider these Renesas ARM based SoC fixes for v4.6.
> > > > > 
> > > > > 
> > > > > Allow serial to work once again on the Porter board (Revision
> > > > > B) which
> > > > > does not have the oscillator in question mounted.
> > > > Have you tested this on Porter?
> > > I don't have working access to a porter at this time.
> > > 
> > > > 
> > > > I believe there's another change to be made for this revert to
> > > > actually work,
> > > > cfr. "[PATCH] ARM: dts: r8a7791: Don't disable referenced
> > > > optional clocks"
> > > > (https://lkml.org/lkml/2016/4/6/350)
> > > Ok, understood.
> > > 
> > > Could someone verify that?
> > I have added "ARM: dts: r8a7791: Don't disable referenced optional
> > clocks"
> > to the fixes-for-v4.6 branch and plan to push it in a fresh renesas-
> > next
> > tag a little later today.
> > 
> > I would appreciate any review and/or testing on porter of that
> branch.
> 
> I've tested this branch (top commit?3d7277614d29) on a Porter revision
> B board and can confirm the serial console works as expected.
> 
> Feel free to add:
> ? Tested-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Thanks, that is really helpful!

I think I will leave out the extra tag as the patches
in question are already signed off by you.

  reply	other threads:[~2016-04-19 22:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  1:52 [GIT PULL] Renesas ARM Based SoC Fixes for v4.6 Simon Horman
2016-04-11  1:52 ` [PATCH] Revert "ARM: dts: porter: Enable SCIF_CLK frequency and pins" Simon Horman
2016-04-11  7:11 ` [GIT PULL] Renesas ARM Based SoC Fixes for v4.6 Geert Uytterhoeven
2016-04-11 23:02   ` Simon Horman
2016-04-18  4:12     ` Simon Horman
2016-04-19  7:23       ` Geert Uytterhoeven
2016-04-19 22:53         ` Simon Horman
2016-04-19  9:12       ` Sjoerd Simons
2016-04-19 22:54         ` Simon Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-21  3:44 Simon Horman
2016-04-22 15:37 ` Kevin Hilman
2016-04-22 17:09   ` Kevin Hilman

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=20160419225448.GD9826@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 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).