From: Johannes Berg <johannes@sipsolutions.net>
To: Ola Olsson <ola1olsson@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Ola Olsson <ola.olsson@sonymobile.com>
Subject: Re: [PATCH] ocb: use correct "MHz" instead of "MHZ"
Date: Wed, 14 Oct 2015 10:00:42 +0200 [thread overview]
Message-ID: <1444809642.3054.6.camel@sipsolutions.net> (raw)
In-Reply-To: <CABAco3BpY-hU=9MGzovyUfyRgXMynikNbUD3cScievczq2qsKg@mail.gmail.com> (sfid-20151014_093604_196513_8DA0F8F0)
On Wed, 2015-10-14 at 09:36 +0200, Ola Olsson wrote:
> Correct. I have done a macro to utilize the gcc "__attribute__
> ((unused))" and I fully understand that it is not an elegant
> solution.
> I don't want to convince you about merging it since I wouldn't do it
> myself. :)
Yeah, ouch, I don't really want that. Perhaps you can add -Wno-unused
-parameters to your Android makefile.
> > I don't see anything with -Wmissing-field-initializers.
>
> Hmm. I'll try to find out why I get these warnings. Mostly, it is
> about changing "{}" -> "{0}" on stack allocated objects.
> This is what I get when compiling at
> 0ee571d57b8b631658d1a35ad9a906610d6145d3
>
> $ mm -B -j8 2>&1 | grep -i missing-field
> external/iw/scan.c:1863:3: warning: missing initializer for field
> 'type' of 'struct nla_policy' [-Wmissing-field-initializers]
>
Yeah, ok, so technically IIRC ={0} is the standard way of doing this in
C, but everything seems to accept ={} as a natural extension of ={.x=y}
I guess? Not sure I want to fix it - doesn't really seem worth much.
johannes
next prev parent reply other threads:[~2015-10-14 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 7:35 [PATCH] ocb: use correct "MHz" instead of "MHZ" Ola Olsson
2015-10-13 9:14 ` Johannes Berg
2015-10-13 22:42 ` Ola Olsson
2015-10-14 6:52 ` Johannes Berg
2015-10-14 7:36 ` Ola Olsson
2015-10-14 8:00 ` Johannes Berg [this message]
2015-10-14 9:05 ` Ola Olsson
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=1444809642.3054.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ola.olsson@sonymobile.com \
--cc=ola1olsson@gmail.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.