From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [git pull] drm fixes for 5.17-rc8/final
Date: Fri, 11 Mar 2022 08:51:53 +0100 [thread overview]
Message-ID: <c5d6fd7b-54ff-e407-2da8-ea2a6157fbff@leemhuis.info> (raw)
In-Reply-To: <CAPM=9txhThmkeKMjTVXGL+RYQDxBZv2c4syb_3V7WF=8sZhaHQ@mail.gmail.com>
On 11.03.22 06:15, Dave Airlie wrote:
>
> As expected at this stage its pretty quiet, one sun4i mixer fix and
> one i915 display flicker fix.
>
> Thanks,
> Dave.
>
> drm-fixes-2022-03-11:
> drm fixes for v5.17-rc8/final
>
> i915:
> - psr fix screen flicker
>
> sun4i:
> - mixer format fix.
> The following changes since commit ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2:
> [...]
Out of curiosity: I might be missing something, but why wasn't the
(afaics simple) fix for a build problem caused by 9d6366e743f3 ("drm:
fb_helper: improve CONFIG_FB dependency") (merged for v5.16-rc1) not
among these fixes? I mean this one:
https://lore.kernel.org/lkml/20220203093922.20754-1-tzimmermann@suse.de/
It's sitting in next for a few days already:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=eea89dff4c39a106f98d1cb5e4d626f8c63908b9
I already asked a few days ago why this fix was not on track for merging
in this cycle, but I didn't get an answer:
https://lore.kernel.org/lkml/782a683e-c625-8e68-899b-ce56939afece@leemhuis.info/
Fun fact: It seems the problem and at a rough fix were already kinda
known mid November when 9d6366e743f3 was still in next:
https://lore.kernel.org/all/20211117062704.14671-1-rdunlap@infradead.org/
Then the issue was reported again two times in February:
https://lore.kernel.org/dri-devel/CA+G9fYvN0NyaVkRQmA1O6rX7H8PPaZrUAD7=RDy33QY9rUU-9g@mail.gmail.com/
https://lore.kernel.org/lkml/YhofdlzadzRmy7tj@debian/
And the fix is relative simple, that's why I wonder why merging is
delayed. What am I missing?
Ciao, Thorsten
next prev parent reply other threads:[~2022-03-11 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 5:15 Dave Airlie
2022-03-11 5:25 ` pr-tracker-bot
2022-03-11 7:51 ` Thorsten Leemhuis [this message]
2022-03-12 7:46 ` Dave Airlie
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=c5d6fd7b-54ff-e407-2da8-ea2a6157fbff@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®