All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: john stultz <johnstul@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, tglx@linutronix.de, greg.weeks@timesys.com
Subject: Re: [PATCH] PowerPC: remove broken vsyscall code
Date: Tue, 07 Nov 2006 09:18:00 +1100	[thread overview]
Message-ID: <1162851480.28571.358.camel@localhost.localdomain> (raw)
In-Reply-To: <1162850967.29826.62.camel@localhost>

On Mon, 2006-11-06 at 14:09 -0800, john stultz wrote:
> On Tue, 2006-11-07 at 08:46 +1100, Benjamin Herrenschmidt wrote:
> > On Mon, 2006-11-06 at 23:59 +0300, Sergei Shtylyov wrote:
> > > Remove vsyscalls that were broken by the PowerPC generic TOD patch, also
> > > fixing the build breakage due to its bad rebase.
> > > 
> > > The patch has been tested on PPC32 only. I had to preserve the data that
> > > are made visible to userland via /proc/ppc64/systemcfg on PPC64, however
> > > now there are only zeroes there and their affect isn't known to me...
> > > 
> > > Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> > 
> > There is simply no way this will happen !
> 
> I believe this is just a short-term fix so the ppc tod/rt code can be
> tested. I do plan on getting the ppc vsyscall working before we push any
> ppc tod changes to mainline.

Ok.

Ben.

      reply	other threads:[~2006-11-06 22:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 20:59 [PATCH] PowerPC: remove broken vsyscall code Sergei Shtylyov
2006-11-06 21:46 ` Benjamin Herrenschmidt
2006-11-06 22:09   ` john stultz
2006-11-06 22:18     ` 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=1162851480.28571.358.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=greg.weeks@timesys.com \
    --cc=johnstul@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.