From: Alexander Kochetkov <al.kochet@gmail.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
kernel@stlinux.com, Daniel Lezcano <daniel.lezcano@linaro.org>,
Patrice Chotard <patrice.chotard@st.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] clocksource/arm_global_timer: reconfigure clockevents after cpufreq change
Date: Tue, 29 Nov 2016 18:04:06 +0300 [thread overview]
Message-ID: <51F052D4-7A19-40FE-8EC2-CE33684383A4@gmail.com> (raw)
In-Reply-To: <54233c9e-d136-4b85-b2db-bf8658a164e7@arm.com>
> 29 нояб. 2016 г., в 17:51, Marc Zyngier <marc.zyngier@arm.com> написал(а):
>
> That'd be my preferred course of action. I've located some documentation
> over there [1], and page 1126 seems to indicate a profusion of
> additional timers, some of which are in an always-on domain. Seems like
> a much better use of someone's time...
Thank you very much :)
And thank you for great explanation of core problem.
In general, I no longer insist on the inclusion the patch in the kernel.
Thank you guys for the help.
Alexander.
next prev parent reply other threads:[~2016-11-29 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 12:15 Alexander Kochetkov
2016-11-29 12:15 ` Alexander Kochetkov
2016-11-29 13:42 ` Thomas Gleixner
2016-11-29 14:05 ` Alexander Kochetkov
2016-11-29 14:09 ` Thomas Gleixner
2016-11-29 14:14 ` Marc Zyngier
2016-11-29 14:32 ` Thomas Gleixner
2016-11-29 14:51 ` Marc Zyngier
2016-11-29 15:04 ` Alexander Kochetkov [this message]
2016-11-29 14:51 ` Alexander Kochetkov
2016-11-29 15:07 ` Robin Murphy
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=51F052D4-7A19-40FE-8EC2-CE33684383A4@gmail.com \
--to=al.kochet@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=patrice.chotard@st.com \
--cc=tglx@linutronix.de \
/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®