From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4/4] intel_th: Fix a NULL dereference when hub driver is not loaded
Date: Fri, 10 Jul 2020 14:03:03 +0000 [thread overview]
Message-ID: <20200710140304.72DCC2082E@mail.kernel.org> (raw)
In-Reply-To: <20200706161339.55468-5-alexander.shishkin@linux.intel.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 39f4034693b7 ("intel_th: Add driver infrastructure for Intel(R) Trace Hub devices").
The bot has tested the following trees: v5.7.7, v5.4.50, v4.19.131, v4.14.187, v4.9.229, v4.4.229.
v5.7.7: Build OK!
v5.4.50: Build OK!
v4.19.131: Build OK!
v4.14.187: Failed to apply! Possible dependencies:
c2d2c7de972d7 ("intel_th: Don't touch switch routing in host mode")
v4.9.229: Failed to apply! Possible dependencies:
c2d2c7de972d7 ("intel_th: Don't touch switch routing in host mode")
v4.4.229: Failed to apply! Possible dependencies:
c2d2c7de972d7 ("intel_th: Don't touch switch routing in host mode")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-07-10 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 16:13 [PATCH 0/4] intel_th: Fixes for v5.8 Alexander Shishkin
2020-07-06 16:13 ` [PATCH 1/4] intel_th: pci: Add Jasper Lake CPU support Alexander Shishkin
2020-07-06 16:13 ` [PATCH 2/4] intel_th: pci: Add Tiger Lake PCH-H support Alexander Shishkin
2020-07-06 16:13 ` [PATCH 3/4] intel_th: pci: Add Emmitsburg PCH support Alexander Shishkin
2020-07-06 16:13 ` [PATCH 4/4] intel_th: Fix a NULL dereference when hub driver is not loaded Alexander Shishkin
2020-07-10 14:03 ` Sasha Levin [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=20200710140304.72DCC2082E@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@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).