linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Anton Blanchard <anton@ozlabs.org>,
	benh@kernel.crashing.org, paulus@samba.org, npiggin@gmail.com,
	mikey@neuling.org, oohall@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [1/2] powerpc/time: Use clockevents_register_device(), fixing an issue with large decrementer
Date: Thu, 11 Oct 2018 19:35:42 +1100 (AEDT)	[thread overview]
Message-ID: <42W46k4bmjz9sjH@ozlabs.org> (raw)
In-Reply-To: <20181001230105.26040-1-anton@ozlabs.org>

On Mon, 2018-10-01 at 23:01:04 UTC, Anton Blanchard wrote:
> We currently cap the decrementer clockevent at 4 seconds, even on systems
> with large decrementer support. Fix this by converting the code to use
> clockevents_register_device() which calculates the upper bound based on
> the max_delta passed in.
> 
> Signed-off-by: Anton Blanchard <anton@ozlabs.org>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/8b78fdb045de60a4eb35460092bbd3

cheers

  parent reply	other threads:[~2018-10-11  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 23:01 [PATCH 1/2] powerpc/time: Use clockevents_register_device(), fixing an issue with large decrementer Anton Blanchard
2018-10-01 23:01 ` [PATCH 2/2] powerpc/time: Add set_state_oneshot_stopped decrementer callback Anton Blanchard
2018-10-11  8:35 ` Michael Ellerman [this message]
2018-10-14 12:39 ` [PATCH 1/2] powerpc/time: Use clockevents_register_device(), fixing an issue with large decrementer Michael Ellerman

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=42W46k4bmjz9sjH@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=anton@ozlabs.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=npiggin@gmail.com \
    --cc=oohall@gmail.com \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).