From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: libertas warnings on ppc64
Date: Wed, 27 Jun 2007 15:57:28 +0200 [thread overview]
Message-ID: <1182952648.4769.14.camel@johannes.berg> (raw)
In-Reply-To: <1182949470.22423.5.camel@xo-13-A4-25.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Wed, 2007-06-27 at 09:04 -0400, Dan Williams wrote:
> On Tue, 2007-06-26 at 17:00 +0200, Johannes Berg wrote:
> > drivers/net/wireless/libertas/debugfs.c: In function
> > ‘libertas_getscantable’:
> > drivers/net/wireless/libertas/debugfs.c:85: warning: format ‘%08llx’
> > expects type ‘long long unsigned int’, but argument 4 has type ‘u64’
> > drivers/net/wireless/libertas/debugfs.c:85: warning: format ‘%08llx’
> > expects type ‘long long unsigned int’, but argument 4 has type ‘u64’
> >
> > Maybe these were addressed by the current pull request? Thought I'd let
> > you know in any case.
>
> Are you using 'upstream-fixes' or 'libertas'? I just built
> 'upstream-fixes' Monday on a 64-bit machine and came up with no such
> warnings when setting KBUILD_VERBOSE=1 before doing the build.
I thought I was using wireless-dev but I was actually using Linus's
tree, confusion about my build here :)
I guess you fixed these then. I also saw another warning about a
constant that was too large but I forgot what it was. I'll report back
whenever your new code makes it in.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-06-27 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 15:00 libertas warnings on ppc64 Johannes Berg
2007-06-27 13:04 ` Dan Williams
2007-06-27 13:57 ` Johannes Berg [this message]
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=1182952648.4769.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--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