All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@inwestnet.de>
To: John Curry <jcurry@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Some PA-RISC 2.0 Gotchas
Date: Fri, 11 Feb 2000 19:21:55 +0100	[thread overview]
Message-ID: <20000211192155.A4843@abacus.local> (raw)
In-Reply-To: <00ec01bf74b2$f4c6c050$1c80100f@jc356611.cup.hp.com>; from jcurry@cup.hp.com on Fri, Feb 11, 2000 at 09:10:54AM -0800

> But, in the free_area_struc type, the map variable is declared as an integer
> ptr. Depending on the size of
> the bitmap, this will cause the parisc_set_bit  to operate incorrectly. We
> solved this problem by making
> the map variable a unsigned long pointer.

it's very unlikely map isn't a multiple of 8 bytes, but I agree this type
should be changed.

> Hope these are of some use.

Thanks, I'm sure they will.

	Philipp

  parent reply	other threads:[~2000-02-11 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-11 17:10 [parisc-linux] Some PA-RISC 2.0 Gotchas John Curry
2000-02-11 17:52 ` Stan Sieler
2000-02-11 18:21 ` Philipp Rumpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-11 18:38 Christopher Neufeld

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=20000211192155.A4843@abacus.local \
    --to=prumpf@inwestnet.de \
    --cc=jcurry@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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.