From: Andrew Morton <akpm@linux-foundation.org>
To: "Rustad, Mark D" <mark.d.rustad@intel.com>
Cc: Michal Nazarewicz <mina86@mina86.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Hagen Paul Pfeifer <hagen@jauu.net>,
"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: [PATCH 2/2] kernel.h: use __COUNTER__ in min and max macros to avoid -Wshadow warnings
Date: Fri, 12 Sep 2014 17:12:52 -0700 [thread overview]
Message-ID: <20140912171252.a6b651d9ab06edc97c4ff67d@linux-foundation.org> (raw)
In-Reply-To: <19E5FFA3-9630-4FD7-8E8A-2754D14AFEC2@intel.com>
On Fri, 12 Sep 2014 23:43:51 +0000 "Rustad, Mark D" <mark.d.rustad@intel.com> wrote:
> Do you mean the number of warnings enabled, or the number of warning messages being generated?
The latter.
My problem is I use crufty old compilers so a number of the warnings I
see aren't seen by sane people and it' snot worth mucking up the source
to fix them.
otoh crufty new compilers add warnings which I won't see...
next prev parent reply other threads:[~2014-09-13 0:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1409837300.2460.10.camel@jtkirshe-mobl>
2014-09-04 21:38 ` kernel: Resolve a shadow warning Andrew Morton
2014-09-04 23:03 ` Rustad, Mark D
2014-09-11 21:39 ` [PATCH 1/2] include: kernel.h: deduplicate code implementing min*, max* and clamp* macros Michal Nazarewicz
2014-09-11 21:39 ` [PATCH 2/2] kernel.h: use __COUNTER__ in min and max macros to avoid -Wshadow warnings Michal Nazarewicz
2014-09-12 22:40 ` Andrew Morton
2014-09-12 23:37 ` Michal Nazarewicz
2014-09-12 23:48 ` Rustad, Mark D
2014-09-12 23:43 ` Rustad, Mark D
2014-09-13 0:12 ` Andrew Morton [this message]
2014-09-25 15:50 ` [PATCH] include: kernel.h: deduplicate code implementing clamp* macros Michal Nazarewicz
2014-09-25 19:46 ` Hagen Paul Pfeifer
2014-09-26 20:04 ` Michal Nazarewicz
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=20140912171252.a6b651d9ab06edc97c4ff67d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hagen@jauu.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mina86@mina86.com \
--cc=rostedt@goodmis.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 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.