All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/22] SH MTU2 DT support
Date: Wed, 12 Mar 2014 18:04:02 +0000	[thread overview]
Message-ID: <20140312180402.GA28891@katana> (raw)
In-Reply-To: <1393955249-18736-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

[-- Attachment #1: Type: text/plain, Size: 798 bytes --]


> > > The patches are compile-tested only as I lack test hardware. Wolfram,
> > > would you be able to test this series with your CCF support patch set for
> > > RZ/A1H ?
> >
> > Applying to current renesas/devel fails. What is this based on? Or
> > better: is there a branch available somewhere?
> 
> I've just rebased my timers devel branch on top of Simon's latest devel branch 
> and pushed the result to
> 
> 	git://linuxtv.org/pinchartl/fbdev.git timers/devel

Thanks! I merged this into my r7s-ccf branch now. I could boot into a
shell and the printk-timestamps make sense. So, for the whole series

Tested-by: Wolfram Sang <wsa@sang-engineering.com>

Daniel, I assume you use git-filter-branch, or shall I tag every patch
individually?

Kind regards,

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-03-12 18:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 17:47 [PATCH 00/22] SH MTU2 DT support Laurent Pinchart
2014-03-04 17:47 ` [PATCH 22/22] clocksource: sh_mtu2: Add " Laurent Pinchart
2014-03-04 17:47   ` Laurent Pinchart
2014-03-05 13:56 ` [PATCH 00/22] SH MTU2 " Wolfram Sang
2014-03-12  8:29 ` Wolfram Sang
2014-03-12 12:26 ` Laurent Pinchart
2014-03-12 18:04 ` Wolfram Sang [this message]
2014-03-12 18:22 ` 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=20140312180402.GA28891@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-sh@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.