public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: tglx@linutronix.de, mingo@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] clocksource: Fix for 4.11
Date: Thu, 16 Mar 2017 17:42:08 +0100	[thread overview]
Message-ID: <20170316164208.GB6579@mai> (raw)


Hi Thomas, Ingo,

this pull request provides one fix for 4.11:

 - Revert the tcb as sched_clock. The initialization routine for the tcb clock
   is too late and leads to a warning. In order to use the tcb as a sched_clock
   the init sequence must be fixed before. Revert the patch until this is done
   (Romain Izard)

The following changes since commit fa3aa7a54fe6d3abf128f13cd4bbd40eaa48fed2:

  jiffies: Revert bogus conversion of NSEC_PER_SEC to TICK_NSEC (2017-03-07 11:03:28 +0100)

are available in the git repository at:

  https://git.linaro.org/people/daniel.lezcano/linux.git clockevents/4.11-fixes

for you to fetch changes up to 33d8c15559df4f0bce25d7e16ebb5879e249f2e7:

  Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock" (2017-03-11 22:03:34 +0100)

----------------------------------------------------------------
Romain Izard (1):
      Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"

 drivers/clocksource/tcb_clksrc.c | 16 +---------------
 1 file changed, 1 insertion(+), 15 deletions(-)


-- 

 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

             reply	other threads:[~2017-03-16 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 16:42 Daniel Lezcano [this message]
2017-03-16 16:44 ` [PATCH] Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock" Daniel Lezcano

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=20170316164208.GB6579@mai \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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