From: "Om N." <xhandle@gmail.com>
To: "Om N." <xhandle@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: writing portable code based on BITS_PER_LONG?
Date: Sun, 6 Aug 2006 13:08:08 -0700 [thread overview]
Message-ID: <6de39a910608061308t4c9dd9fdo3e1ff634a3079e3d@mail.gmail.com> (raw)
In-Reply-To: <20060806103143.GR20586@lug-owl.de>
On 8/6/06, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> On Sat, 2006-08-05 23:16:29 -0700, Om N. <xhandle@gmail.com> wrote:
> > I am trying to port a driver written for IA32. This is a pci driver
> > and has a chipset doing PCI <-> local bus data transfer, where local
> > bus is 16 bit. So a number of values are converted by right/left
> > shifting by 16 bits.
> I'd probably write some macros that access the parts of the longs you
> want to have/set and put these into some header file.
Let me go the macro way. Let me beat the code into some shape and then
post a url to the list for comments on 64bit safeness.
Thanks for ideas,
Regards,
Om.
next prev parent reply other threads:[~2006-08-06 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 6:16 Om N.
2006-08-06 10:31 ` Jan-Benedict Glaw
2006-08-06 20:08 ` Om N. [this message]
2006-08-06 16:12 ` Arjan van de Ven
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=6de39a910608061308t4c9dd9fdo3e1ff634a3079e3d@mail.gmail.com \
--to=xhandle@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®