From: Guenter Roeck <linux@roeck-us.net>
To: stable@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>
Cc: Ahsan Hussain <ahsan_hussain@mentor.com>,
Sasha Levin <alexander.levin@microsoft.com>
Subject: Please apply commit 0c4c5860e998 to v4.4.y, v4.9.y, v4.14.y, v4.15.y
Date: Mon, 16 Apr 2018 11:43:24 -0700 [thread overview]
Message-ID: <20180416184324.GA14023@roeck-us.net> (raw)
Hi Greg,
Upstream commit 0c4c5860e998 ("hwmon: (ina2xx) Fix access to uninitialized
mutex") fixes commit 5d389b125186 ("hwmon: (ina2xx) Make calibration register
value fixed"), which has found its way into v4.4.y, v4.9.y, v4.14.y, and
v4.15.y.
Please apply commit 0c4c5860e998 to all affected releases to fix the
resulting regression.
Maybe Sasha's script could be improved to look for Fixes: tags when
suggesting to apply patches to older releases.
Thanks,
Guenter
next reply other threads:[~2018-04-16 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 18:43 Guenter Roeck [this message]
2018-04-17 11:10 ` Please apply commit 0c4c5860e998 to v4.4.y, v4.9.y, v4.14.y, v4.15.y Greg KH
2018-04-17 13:26 ` Guenter Roeck
2018-04-17 14:50 ` Greg KH
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=20180416184324.GA14023@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ahsan_hussain@mentor.com \
--cc=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--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).