From: Sasha Levin <sasha.levin@oracle.com>
To: Yuki Machida <machida.yuki@jp.fujitsu.com>
Cc: stable@vger.kernel.org, jcboyd.dev@gmail.com, jkosina@suse.cz
Subject: Re: Backport 09a5c3 ("HID: hid-input: Add parentheses to quell gcc warning") to 4.1.y
Date: Tue, 14 Jun 2016 18:15:39 -0400 [thread overview]
Message-ID: <5760820B.9040905@oracle.com> (raw)
In-Reply-To: <575FC235.4020701@jp.fujitsu.com>
On 06/14/2016 04:37 AM, Yuki Machida wrote:
> Hi Sasha,
>
> I conformed that v4.1.26 has a same warning using gcc 5.2.0.
> Please apply following patch to 4.1.y.
> 09a5c34e8d6b05663ec4c3d22b1fbd9fec89aaf9
Is there an actual bug fix here? It looks like this is just a warning,
but the code itself is fine.
Thanks,
Sasha
next prev parent reply other threads:[~2016-06-14 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 8:37 Backport 09a5c3 ("HID: hid-input: Add parentheses to quell gcc warning") to 4.1.y Yuki Machida
2016-06-14 22:15 ` Sasha Levin [this message]
2016-06-15 8:35 ` Yuki Machida
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=5760820B.9040905@oracle.com \
--to=sasha.levin@oracle.com \
--cc=jcboyd.dev@gmail.com \
--cc=jkosina@suse.cz \
--cc=machida.yuki@jp.fujitsu.com \
--cc=stable@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).