Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Torsten Neumann <torsten@imke.infodrom.ffis.de>,
	Peter Weilbacher <weilbach@uni-sw.gwdg.de>,
	parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] unaligned memory accesses
Date: Wed, 4 Jul 2001 15:51:08 -0700	[thread overview]
Message-ID: <20010704155108.H31475@tausq.org> (raw)

Torsten and Peter,

I've checked in some changes to parisc kernel cvs that should address 
the crashes you've seen. Please try picking up latest kernel files from 
cvs and let us know if they fix the errors you've seen.

thanks,
randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

             reply	other threads:[~2001-07-04 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 22:51 Randolph Chung [this message]
2001-07-05 18:15 ` [parisc-linux] Re: unaligned memory accesses Torsten Neumann
2001-07-05 19:04   ` Randolph Chung
2001-07-05 20:04     ` Torsten Neumann

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=20010704155108.H31475@tausq.org \
    --to=randolph@tausq.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=torsten@imke.infodrom.ffis.de \
    --cc=weilbach@uni-sw.gwdg.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