mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: bit ops on unsigned long?
Date: Sun, 24 Mar 2002 19:45:26 -0700	[thread overview]
Message-ID: <200203250245.g2P2jQa20821@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <E16m4YD-0004af-00@wagner.rustcorp.com.au>

Rusty Russell writes:
> Richard: 3 bugs in devfs.  Particularly note that the memset was
> bogus.  I can't convince myself that your memcpy & memset stuff is
> right anyway, given that you can ONLY treat them as unsigned longs
> (ie. bit 31 will be in byte 0 or byte 3, depending on endianness).

Yes, the memset is bogus because I didn't cast the pointer to a
char * or void *. The memcpy should be fine, though. And so should
everything else, because the bitfield array is allocated in 16 byte
multiples. So there should be no issues with big vs. little endian,
since memset/memcpy operations are done in blocks of sufficient
alignment.

So, really, the only problem is the stupid lack of a cast. Unless you
noticed some other problem?

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2002-03-25  2:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16  0:52 Rusty Russell
2002-03-16  0:58 ` Linus Torvalds
2002-03-16  3:08   ` Rusty Russell
2002-03-25  2:45     ` Richard Gooch [this message]
2002-03-25  4:27       ` Rusty Russell
2002-03-25  6:21         ` Richard Gooch
2002-03-25  7:07           ` Rusty Russell
2002-03-25  7:12             ` Richard Gooch
2002-03-18  4:08   ` David S. Miller
2002-03-18  6:03     ` Jeff Garzik
2002-03-18  6:43       ` David S. Miller
2002-03-18  9:13       ` Rusty Russell
2002-03-16  1:00 ` Anton Blanchard

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=200203250245.g2P2jQa20821@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®