From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Lyude Paul <lyude@redhat.com>
To: nouveau@lists.freedesktop.org
Cc: stable@vger.kernel.org, Ben Skeggs <bskeggs@redhat.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v4] drm/nouveau/kms/nv50-: Program notifier offset before requesting disp caps
Date: Wed, 02 Sep 2020 13:38:45 +0000 [thread overview]
Message-ID: <20200902133846.9C12A20767@mail.kernel.org> (raw)
In-Reply-To: <20200901234240.197917-1-lyude@redhat.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 4a2cb4181b07 ("drm/nouveau/kms/nv50-: Probe SOR and PIOR caps for DP interlacing support").
The bot has tested the following trees: v5.8.5.
v5.8.5: Failed to apply! Possible dependencies:
0a96099691c8 ("drm/nouveau/kms/nv50-: implement proper push buffer control logic")
0bc8ffe09771 ("drm/nouveau/kms/nv50-: Move hard-coded object handles into header")
12885ecbfe62 ("drm/nouveau/kms/nvd9-: Add CRC support")
203f6eaf4182 ("drm/nouveau/kms/nv50-: convert core update() to new push macros")
2853ccf09255 ("drm/nouveau/kms/nv50-: wrap existing command submission in nvif_push interface")
344c2e5a4796 ("drm/nouveau/kms/nv50-: use NVIDIA's headers for core or_ctrl()")
3c43c362b3a5 ("drm/nouveau/kms/nv50-: convert core caps_init() to new push macros")
5e691222eac6 ("drm/nouveau/kms/nv50-: convert core init() to new push macros")
9ec5e8204053 ("drm/nouveau/kms/nv50-: convert core or_ctrl() to new push macros")
b11d8ca151d0 ("drm/nouveau/kms/nv50-: use NVIDIA's headers for core init()")
b505935e56b2 ("drm/nouveau/kms/nv50-: convert core wndw_owner() to new push macros")
d8b24526ef68 ("drm/nouveau/kms/nv50-: use NVIDIA's headers for core caps_init()")
e79c9a0ba5e7 ("drm/nouveau/nvif: give every mem object a human-readable identifier")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-09-02 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200824183253.826343-1-lyude@redhat.com>
2020-08-24 18:32 ` [PATCH 1/2] drm/nouveau/kms/nv50-: Program notifier offset before requesting disp caps Lyude Paul
2020-08-24 22:28 ` [Nouveau] " Ben Skeggs
2020-08-25 16:52 ` Lyude Paul
2020-08-31 4:26 ` Ben Skeggs
2020-09-01 20:43 ` Lyude Paul
2020-09-01 23:38 ` [PATCH v3] " Lyude Paul
2020-09-01 23:42 ` [PATCH v4] " Lyude Paul
2020-09-02 13:38 ` Sasha Levin [this message]
2020-09-03 5:15 ` [Nouveau] " Ben Skeggs
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=20200902133846.9C12A20767@mail.kernel.org \
--to=sashal@kernel.org \
--cc=bskeggs@redhat.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;
as well as URLs for NNTP newsgroup(s).