From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>, Lyude <lyude@redhat.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: thinkpad_acpi: Initialize local in_tablet_mode and type
Date: Thu, 15 Dec 2016 13:16:55 -0800 [thread overview]
Message-ID: <20161215211655.GA39589@f23x64.localdomain> (raw)
In-Reply-To: <1481825702.9552.44.camel@linux.intel.com>
On Thu, Dec 15, 2016 at 08:15:02PM +0200, Andy Shevchenko wrote:
> On Wed, 2016-12-14 at 20:14 -0800, Darren Hart wrote:
> > linux-next reported in_tablet_mode and type may be used uninitialized
> > after:
> >
> > b31800283868 ("platform/x86: thinkpad_acpi: Move tablet detection into
> > separate function")
> >
> > This turns out to be a false positive as the pr_info call cannot be
> > reached if tp_features.hotkey_tablet (global scope) is 0, and
> > in_tablet_mode and type are assigned in both places
> > tp_features.hotkey_tablet is assigned.
> >
> > Regardless, to make it explicit and avoid further reports, initialize
> > in_tablet_mode to 0 and type to "".
> >
>
> @@ -3143,8 +3143,8 @@ typedef tpacpi_keymap_entry_t
> > tpacpi_keymap_t[TPACPI_HOTKEY_MAP_LEN];
> >
> > static int hotkey_init_tablet_mode(void)
> > {
> > - int in_tablet_mode, res;
> > - char *type;
> > + int in_tablet_mode = 0, res;
> > + char *type = "";
>
> Subtle correction
> NULL will work either and takes less memory ;)
>
> P.S. Even pr_*() is NULL-aware
Agreed. Fixed, pushed, tagged. Thanks all.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2016-12-15 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 4:14 [PATCH v2] platform/x86: thinkpad_acpi: Initialize local in_tablet_mode and type Darren Hart
2016-12-15 12:44 ` Henrique de Moraes Holschuh
2016-12-15 18:15 ` Andy Shevchenko
2016-12-15 21:16 ` Darren Hart [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=20161215211655.GA39589@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=platform-driver-x86@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