From: Guenter Roeck <linux@roeck-us.net>
To: stable@vger.kernel.org, gregkh@linuxfoundation.org, sashal@kernel.org
Subject: Patches missing from v4.14.y/v4.19.y after most recent stable release
Date: Wed, 20 Nov 2019 14:02:38 -0800 [thread overview]
Message-ID: <20191120220238.GA21382@roeck-us.net> (raw)
Hi,
when merging the most recent stable releases into chromeos-4.14 and
chromeos-4.19, I noticed that the following patches are missing
in v4.14.y and v4.19.y. In both cases a backported fix was later fixed
upstream, but the fix of the fix was not backported.
v4.14.y, v4.19.y:
commit a4d8f64f7267 ("spi: mediatek: use correct mata->xfer_len when in fifo transfer")
Fixes commit 6237e9d0715a ("spi: mediatek: Don't modify spi_transfer
when transfer."), but is not marked for stable/fixes.
v4.19.y:
commit bc1a7f75c85e ("i2c: mediatek: modify threshold passed to i2c_get_dma_safe_msg_buf()")
Fixes: fc66b39fe36a ("i2c: mediatek: Use DMA safe buffers for i2c transactions")
Please consider applying the missing patches to future stable releases.
Thanks,
Guenter
next reply other threads:[~2019-11-20 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 22:02 Guenter Roeck [this message]
2019-11-21 6:53 ` Patches missing from v4.14.y/v4.19.y after most recent stable release Greg KH
2019-11-21 9:42 ` Guenter Roeck
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=20191120220238.GA21382@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.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).