From: David Miller <davem@davemloft.net>
To: hs4233@mail.mn-solutions.de
Cc: linux-wireless@vger.kernel.org
Subject: Re: libertas warnings in upstream
Date: Wed, 13 Jun 2007 01:06:10 -0700 (PDT) [thread overview]
Message-ID: <20070613.010610.08321860.davem@davemloft.net> (raw)
In-Reply-To: <200706130953.57827.hs4233@mail.mn-solutions.de>
From: Holger Schurig <hs4233@mail.mn-solutions.de>
Date: Wed, 13 Jun 2007 09:53:57 +0200
> > Tried to test-compile libertas on a 64-bit platform.
>
> I don't have a 64 bit machine and can't therefore say anything
> about those 64 issues. However, sparse doesn't moan about
> anything, not sure if sparse checks 64bit issues on a 32bit
> machine.
You don't need 64-bit hardware, don't use this as a reason,
it's invalid.
There are lots of cross-build setups available out there, precompiled
and everything.
sparse can do 64-bit checking if you build using it for a 64-bit
target. So if you have a cross compile setup, sparse will also do the
right thing.
next prev parent reply other threads:[~2007-06-13 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 7:25 libertas warnings in upstream Meelis Roos
2007-06-13 7:53 ` Holger Schurig
2007-06-13 8:06 ` David Miller [this message]
2007-06-13 9:26 ` Meelis Roos
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=20070613.010610.08321860.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@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