From: Sasha Levin <sashal@kernel.org>
To: Ross Zwisler <zwisler@chromium.org>
Cc: stable@vger.kernel.org, Ross Zwisler <zwisler@google.com>,
Dave Airlie <airlied@redhat.com>,
Guenter Roeck <groeck@google.com>
Subject: Re: [v4.14.y PATCH 0/2] fix drm/udl use-after-free error
Date: Mon, 15 Jul 2019 21:13:08 -0400 [thread overview]
Message-ID: <20190716011308.GA1943@sasha-vm> (raw)
In-Reply-To: <20190715193618.24578-1-zwisler@google.com>
On Mon, Jul 15, 2019 at 01:36:16PM -0600, Ross Zwisler wrote:
>This patch is the second in this series, and requires the first patch as
>a dependency. This series apples cleanly to v4.14.133.
Hm, we don't need ac3b35f11a06 here? Why not? I'd love to document that
with the backport.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-07-16 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 19:36 [v4.14.y PATCH 0/2] fix drm/udl use-after-free error Ross Zwisler
2019-07-15 19:36 ` [v4.14.y PATCH 1/2] drm/udl: introduce a macro to convert dev to udl Ross Zwisler
2019-07-15 19:36 ` [v4.14.y PATCH 2/2] drm/udl: move to embedding drm device inside udl device Ross Zwisler
2019-07-16 1:13 ` Sasha Levin [this message]
2019-07-16 16:08 ` [v4.14.y PATCH 0/2] fix drm/udl use-after-free error Ross Zwisler
2019-07-17 23:28 ` Sasha Levin
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=20190716011308.GA1943@sasha-vm \
--to=sashal@kernel.org \
--cc=airlied@redhat.com \
--cc=groeck@google.com \
--cc=stable@vger.kernel.org \
--cc=zwisler@chromium.org \
--cc=zwisler@google.com \
/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).