From: Guenter Roeck <linux@roeck-us.net>
To: "Moore, Robert" <robert.moore@intel.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"Zheng, Lv" <lv.zheng@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: Re: [PATCH v2] acpi: Use kstrtoul() instead of strtoul()/simple_strtoul()
Date: Wed, 29 Jul 2015 11:38:39 -0700 [thread overview]
Message-ID: <55B91DAF.3060605@roeck-us.net> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D329493@ORSMSX112.amr.corp.intel.com>
On 07/29/2015 10:51 AM, Moore, Robert wrote:
>
>
>> -----Original Message-----
>> From: Guenter Roeck [mailto:linux@roeck-us.net]
>> Sent: Monday, July 27, 2015 5:32 PM
>> To: rjw@rjwysocki.net
>> Cc: lenb@kernel.org; Moore, Robert; Zheng, Lv; linux-acpi@vger.kernel.org;
>> linux-kernel@vger.kernel.org; devel@acpica.org; Guenter Roeck
>> Subject: [PATCH v2] acpi: Use kstrtoul() instead of
>> strtoul()/simple_strtoul()
>>
>> simple_strtoul() is deprecated; replace with kstrtoul() and kstrtouint().
>
> The ACPICA code is os-independent and cannot use these functions (at least not directly).
>
>
Odd argument, given that kstrtoul() is used already in the acpi code.
Guenter
next prev parent reply other threads:[~2015-07-29 18:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 0:32 [PATCH v2] acpi: Use kstrtoul() instead of strtoul()/simple_strtoul() Guenter Roeck
2015-07-29 17:51 ` Moore, Robert
2015-07-29 17:51 ` [Devel] " Moore, Robert
2015-07-29 18:38 ` Guenter Roeck [this message]
2015-07-29 19:33 ` Moore, Robert
2015-07-29 19:33 ` [Devel] " Moore, Robert
2015-07-29 19:58 ` Guenter Roeck
2015-07-29 20:04 ` Rafael J. Wysocki
2015-07-29 20:37 ` Guenter Roeck
2015-07-29 19:57 ` Rafael J. Wysocki
2015-08-02 7:16 ` Pavel Machek
2015-08-02 8:19 ` Guenter Roeck
2015-11-06 16:21 ` Moore, Robert
2015-11-06 16:21 ` [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=55B91DAF.3060605@roeck-us.net \
--to=linux@roeck-us.net \
--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=rjw@rjwysocki.net \
--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 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.