Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Florian Lohoff <flo@rfc822.org>,
	libc-alpha@sources.redhat.com, Klaus Naumann <spock@mgnet.de>,
	Robert Einsle <robert@einsle.de>,
	linux-mips@oss.sgi.com
Subject: Re: Probs running ntp on an indy
Date: Fri, 20 Jul 2001 08:04:41 +0200	[thread overview]
Message-ID: <u8snfsb0g6.fsf@gromit.moeb> (raw)
In-Reply-To: <20010719142009.A26517@nevyn.them.org> (Daniel Jacobowitz's message of "Thu, 19 Jul 2001 14:20:09 -0700")

Daniel Jacobowitz <dan@debian.org> writes:

> On Thu, Jul 19, 2001 at 10:51:37PM +0200, Florian Lohoff wrote:
>> On Thu, Jul 19, 2001 at 10:24:06PM +0200, Klaus Naumann wrote:
>> > I know the problem but no solution. I suspect that it's a
>> > problem of the poll function in Big Endian environments, because
>> > I can reproduce this on my Indigo2 and on an Ultra 1 as well.
>> 
>> I remember seeing a patch concerning this problem - Something with
>> rtsignals - But i cant seem to find it anymore.
> 
> That's probably this one.  I knew I'd let a patch slip.  Glibc folk, is
> this OK?  The siginfo struct is different on MIPS.

Yes, that's fine.

Thanks, I've committed it,
Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

      reply	other threads:[~2001-07-20  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 17:26 Probs running ntp on an indy Robert Einsle
2001-07-19 20:24 ` Klaus Naumann
2001-07-19 20:51   ` Florian Lohoff
2001-07-19 21:20     ` Daniel Jacobowitz
2001-07-20  6:04       ` Andreas Jaeger [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=u8snfsb0g6.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=dan@debian.org \
    --cc=flo@rfc822.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=robert@einsle.de \
    --cc=spock@mgnet.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