From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Len Brown <len.brown@intel.com>,
Jean Delvare <khali@linux-fr.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: Constify 'type' argument for the registration routine
Date: Tue, 19 Jun 2012 18:25:41 -0700 [thread overview]
Message-ID: <20120620012541.GA3564@lizard> (raw)
In-Reply-To: <20120619171128.377fc971.akpm@linux-foundation.org>
On Tue, Jun 19, 2012 at 05:11:28PM -0700, Andrew Morton wrote:
> On Sun, 17 Jun 2012 21:50:37 -0700
> Anton Vorontsov <anton.vorontsov@linaro.org> wrote:
>
> > thermal_zone_device_register() does not modify 'type' argument, so
> > it is safe to declare it as const. Otherwise, if we pass a const
> > string, we are getting the ugly warning:
> >
> > ...
> >
>
> For some reason I can't apply this.
The reason is the same patch in ACPI tree that "broke" battery tree;
we're just touching the same lines of code and that causes some pain.
> I typed it in again and it seems
> to work OK. I'll assume that someone else will merge it into
> whatever-tree-broke.
Len, will you merge this patch? Or should I take it into battery
tree? (If I'm taking it, then Stephen will have to resolve some
conflicts upon next -next tree generation.)
> > +struct thermal_zone_device *
> > +thermal_zone_device_register(const char *, int, void *,
> > const struct thermal_zone_device_ops *, int tc1, int tc2,
> > int passive_freq, int polling_freq);
> > void thermal_zone_device_unregister(struct thermal_zone_device *);
>
> Personally, I prefer it when the arguments are named in the declaration
> - if you ever have reason to *read* the thing, the lack of names is
> quite maddening. Particularly when the function has 72 arguments.
:-)
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
prev parent reply other threads:[~2012-06-20 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 4:50 [PATCH] thermal: Constify 'type' argument for the registration routine Anton Vorontsov
2012-06-18 6:19 ` Jean Delvare
2012-06-20 0:11 ` Andrew Morton
2012-06-20 1:25 ` Anton Vorontsov [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=20120620012541.GA3564@lizard \
--to=cbouatmailru@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.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;
as well as URLs for NNTP newsgroup(s).