linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH/RFC] powerpc: Fix decrementer setup on 1GHz boards
Date: Fri, 09 Oct 2009 17:27:15 +1100	[thread overview]
Message-ID: <1255069635.2861.0.camel@pasglop> (raw)
In-Reply-To: <200910090728.28870.sr@denx.de>

On Fri, 2009-10-09 at 07:28 +0200, Stefan Roese wrote:
> 
> So how could we solve this issue now? Apply my current patch? Any
> other suggestions? 

Well, we probably need your current patch, but I'm not 100% it's enough.
We need to check for example that the vDSO code for 32-bit isn't going
to go out of bounds neither.

Cheers,
Ben.

      reply	other threads:[~2009-10-09  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 14:49 [PATCH/RFC] powerpc: Fix decrementer setup on 1GHz boards Stefan Roese
2009-10-08 20:12 ` Benjamin Herrenschmidt
2009-10-09  5:28   ` Stefan Roese
2009-10-09  6:27     ` Benjamin Herrenschmidt [this message]

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=1255069635.2861.0.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.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;
as well as URLs for NNTP newsgroup(s).