From: Joe Perches <joe@perches.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: LABBE Corentin <clabbe.montjoie@gmail.com>,
"Zheng, Lv" <lv.zheng@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Box, David E" <david.e.box@intel.com>
Subject: Re: [PATCH] acpi: set return value to const char for some functions
Date: Thu, 15 Oct 2015 16:59:46 -0700 [thread overview]
Message-ID: <1444953586.22921.0.camel@perches.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D9806CC@ORSMSX112.amr.corp.intel.com>
On Thu, 2015-10-15 at 19:32 +0000, Moore, Robert wrote:
> if you started to use "const" for some methods you usually forced to
> use this in most of your code. But the time spent for maintaining
> (typing, recompiling when some const is missing, etc.) of
> const-correctness in code seems greater than for fixing of possible
> (very rare) problems caused by not using of const-correctness at all
c is not c++.
"seems" is a dubious statement.
next prev parent reply other threads:[~2015-10-15 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 19:07 [PATCH] acpi: set return value to const char for some functions LABBE Corentin
2015-10-14 19:48 ` kbuild test robot
2015-10-14 20:53 ` Moore, Robert
2015-10-15 2:14 ` Joe Perches
2015-10-15 19:32 ` Moore, Robert
2015-10-15 23:59 ` Joe Perches [this message]
2015-10-16 3:37 ` Moore, Robert
2015-10-16 3:47 ` Joe Perches
2015-10-19 12:02 ` LABBE Corentin
2015-10-19 17:04 ` Moore, Robert
2015-10-19 17:15 ` Moore, Robert
2015-10-21 17:44 ` [Devel] " Moore, Robert
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=1444953586.22921.0.camel@perches.com \
--to=joe@perches.com \
--cc=clabbe.montjoie@gmail.com \
--cc=david.e.box@intel.com \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox