From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast
Date: Wed, 17 Dec 2014 14:43:09 +0000 [thread overview]
Message-ID: <1970614.16PkIBYMHz@avalon> (raw)
In-Reply-To: <20141216094854.22639.69181.sendpatchset@w520>
Hi Geert,
On Wednesday 17 December 2014 14:59:21 Geert Uytterhoeven wrote:
> On Wed, Dec 17, 2014 at 1:14 PM, Laurent Pinchart wrote:
> >>> What are we missing ?
> >>>
> >>> - The DIV6 multiparent series has been merged by Mike, and the sh73a0
> >>> CCF is nearly ready.
> >>
> >> Yep.
> >>
> >>> - We need proper BSC support to get LAN working, although it could be
> >>> worked around temporarily by specifying the BSC clock in the LAN node
> >>> if I recall correctly.
> >>
> >> Working on that. I hope to send out v2 later today...
> >>
> >>> - Accelerometer and RTC have no DT bindings, but they should work with
> >>> the I2C core OF match support.
> >>
> >> I have RTC in my DTS, and it works.
> >
> > Great.
> >
> > I can help with at least some of the remaining pieces if you share your
> > working branch.
>
> I pushed my local working branch to
> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git/log/?
> h=wip
>
> Please wear sun glasses, and keep the kbuild test robot away ;-)
I will :-) Thank you. Is there a way to selectively keep kbuild away from
branches by the way ?
Do avoid duplicating work, what do you plan to work on in the context of
multiplatform kzm9g ?
Magnus, how much time do you think would be worth spending on DT support for
the lcdc drm driver ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-17 14:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 9:48 [PATCH] clocksource: sh_tmu: Set cpu_possible_mask to fix SMP broadcast Magnus Damm
2014-12-16 11:14 ` Daniel Lezcano
2014-12-16 11:20 ` Laurent Pinchart
2014-12-16 11:25 ` Laurent Pinchart
2014-12-16 11:29 ` Daniel Lezcano
2014-12-16 11:46 ` Magnus Damm
2014-12-16 11:54 ` Daniel Lezcano
2014-12-17 0:44 ` Laurent Pinchart
2014-12-16 12:40 ` Geert Uytterhoeven
2014-12-17 1:30 ` Magnus Damm
2014-12-17 2:08 ` Laurent Pinchart
2014-12-17 8:30 ` Geert Uytterhoeven
2014-12-17 9:42 ` Geert Uytterhoeven
2014-12-17 12:04 ` Laurent Pinchart
2014-12-17 12:11 ` Geert Uytterhoeven
2014-12-17 12:14 ` Laurent Pinchart
2014-12-17 11:31 ` Laurent Pinchart
2014-12-17 13:23 ` Magnus Damm
2014-12-19 0:03 ` Magnus Damm
2014-12-19 0:46 ` Laurent Pinchart
2014-12-17 8:25 ` Geert Uytterhoeven
2014-12-17 0:43 ` Laurent Pinchart
2014-12-17 13:59 ` Geert Uytterhoeven
2014-12-17 14:43 ` Laurent Pinchart [this message]
2014-12-17 15:34 ` Laurent Pinchart
2014-12-17 15:44 ` Geert Uytterhoeven
2014-12-17 15:46 ` Magnus Damm
2014-12-18 3:29 ` 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=1970614.16PkIBYMHz@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox