Message ID | CAPM=9txhThmkeKMjTVXGL+RYQDxBZv2c4syb_3V7WF=8sZhaHQ@mail.gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [git,pull] drm fixes for 5.17-rc8/final | expand |
The pull request you sent on Fri, 11 Mar 2022 15:15:09 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2022-03-11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/79b00034e9dcd2b065c1665c8b42f62b6b80a9be
Thank you!
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
On Fri, 11 Mar 2022 at 17:51, Thorsten Leemhuis <regressions@leemhuis.info> wrote: > > 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? My radar just missed it, though someone else should have realised it was necessary on fixes earlier, it also had incorrect Fixes: tagging, so I fixed that and sent it to Linus, Thanks, Dave.