From: Ben Hutchings <ben@decadent.org.uk>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: stable <stable@vger.kernel.org>
Subject: Unneeded commits in 3.16-ckt branch?
Date: Mon, 18 May 2015 00:20:23 +0100 [thread overview]
Message-ID: <1431904823.6315.164.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
So far as I can see, the following commits don't fix bugs in 3.16. But
I don't know that they cause any problems, either.
commit aba636b877ec270075cbb01b4fceb460f0c3f07a
Author: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Date: Thu Apr 16 13:05:19 2015 +0100
i2c: Mark adapter devices with pm_runtime_no_callbacks
commit 6ada5c1e1b077ab98fc144d7ac132b4dcc0148ec upstream.
- fixes regression in 4.0
commit 65342eab7baa43fb7852aafbe99e54daf2cd6420
Author: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Date: Tue Apr 14 15:42:30 2015 -0700
mm/hugetlb: use pmd_page() in follow_huge_pmd()
commit 97534127012f0e396eddea4691f4c9b170aed74b upstream.
- fixes regression in 4.0
commit 9c518c0eac18b0f0e13666ae67aa0a7e87a81032
Author: Eric Dumazet <edumazet@google.com>
Date: Thu Apr 9 13:31:56 2015 -0700
tcp: tcp_make_synack() should clear skb->tstamp
commit b50edd7812852d989f2ef09dcfc729690f54a42d upstream.
- fixes regression in 3.18
commit 46f080a6f59fd58de1acb4ccadf3a8b5f934659a
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: Tue Apr 21 09:49:11 2015 -0700
drm/i915: cope with large i2c transfers
commit 9535c4757b881e06fae72a857485ad57c422b8d2 upstream.
- needed for feature introduced in 3.17
--
Ben Hutchings
Never put off till tomorrow what you can avoid all together.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next reply other threads:[~2015-05-17 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 23:20 Ben Hutchings [this message]
2015-05-18 9:49 ` Unneeded commits in 3.16-ckt branch? Luis Henriques
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=1431904823.6315.164.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=luis.henriques@canonical.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