From: Thomas Gleixner <tglx@linutronix.de>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Baruch Siach <baruch@tkos.co.il>,
John Stultz <john.stultz@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
Michal Simek <michal.simek@xilinx.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] clocksource/cadence_ttc: Reuse clocksource as sched_clock
Date: Fri, 5 Jul 2013 22:59:53 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1307052259090.32106@ionos.tec.linutronix.de> (raw)
In-Reply-To: <4fab6223-45c5-453e-9972-1c12aa79a312@CO1EHSMHS008.ehs.local>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 812 bytes --]
On Fri, 5 Jul 2013, Sören Brinkmann wrote:
> On Fri, Jul 05, 2013 at 10:42:03PM +0200, Thomas Gleixner wrote:
> > We have a mechanism for that in place, if stuff goes cross trees. One
> > of the trees provides a set of commit for the other tree to pull, so
> > we do not end up with merge dependencies and conflicts.
> >
> > Why is clocksource stuff going through armsoc unless it contains
> > related modifications in arch/arm/
> We overhauled Zynq's common clock code and migrated all Zynq drivers to
> it - the TTC being one. I'm pretty sure you were on the CC list for that
> change.
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30e1e28598c2674c133148d8aec6d431d7acd314
>
That's fine as it has no dependencies on any of the clocksource core
changes AFAICT.
Thanks,
tglx
next prev parent reply other threads:[~2013-07-05 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 21:50 Soren Brinkmann
2013-07-04 3:30 ` Baruch Siach
2013-07-05 20:12 ` Sören Brinkmann
2013-07-05 20:42 ` Thomas Gleixner
2013-07-05 20:56 ` Sören Brinkmann
2013-07-05 20:59 ` Thomas Gleixner [this message]
2013-07-05 21:10 ` Sören Brinkmann
2013-07-05 6:30 ` Thomas Gleixner
2013-07-05 15:43 ` Sören Brinkmann
2013-07-05 16:05 ` Thomas Gleixner
2013-07-05 16:12 ` Sören Brinkmann
2013-07-05 16:23 ` Thomas Gleixner
2013-07-08 16:27 ` Sören Brinkmann
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=alpine.DEB.2.02.1307052259090.32106@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=baruch@tkos.co.il \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=soren.brinkmann@xilinx.com \
/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
all inboxes | Powered by JetHome®