linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel@ffwll.ch>, Helge Deller <deller@gmx.de>,
	linux-fbdev@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>
Subject: Re: [GIT PULL] fbdev updates & fixes for v5.17-rc1
Date: Fri, 21 Jan 2022 09:19:49 +0000	[thread overview]
Message-ID: <Yep6te0wrK0ZQ8SB@google.com> (raw)
In-Reply-To: <87fsph4fr2.fsf@intel.com>

On Fri, 21 Jan 2022, Jani Nikula wrote:

> On Fri, 21 Jan 2022, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Jan 19, 2022 at 5:02 PM Helge Deller <deller@gmx.de> wrote:
> >> A first bunch of updates and fixes for the following fbdev & backlight drivers:
> >> ocfb, aty128fb, mb862xx, omapfb, qcom-wled, dt-bindings, hyperv_fb,
> >> lm3630a_bl, omap2, controlfb, matroxfb
> >>
> >> Nothing really important, mostly cleanups, const conversions, added null
> >> pointer/boundary checks and build fixes.
> >>
> >> Signed-off-by: Helge Deller <deller@gmx.de>
> >
> > Not sure whether Linus missed this or just wanted to let the
> > discussion settle first. But since this is all random patches for
> > drivers that many distros don't even enable anymore there's no issues
> > here, and I very much welcome someone volunteering to pick these up.
> > I'd expect there's a pile more since it's been 1-2 years since Bart
> > took care of these and merged them consistently.
> >
> > Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> ...
> 
> >>  drivers/video/backlight/lm3630a_bl.c                     |  1 -
> >>  drivers/video/backlight/qcom-wled.c                      |  1 +
> 
> Backlight changes usually go through the backlight tree.

Yes, they do.  How were these applied to the DRM tree?

I don't see any mails about them being applied:

  Luca Weiss (2):
        backlight: qcom-wled: Add PM6150L compatible

  https://lore.kernel.org/all/20211229170358.2457006-2-luca.weiss@fairphone.com/

  Xu Wang (2):
        backlight: lm3630a_bl: Remove redundant 'flush_workqueue()' calls

  https://lore.kernel.org/all/20220113084806.13822-1-vulab@iscas.ac.cn/

-- 
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2022-01-21  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 16:01 [GIT PULL] fbdev updates & fixes for v5.17-rc1 Helge Deller
2022-01-21  8:47 ` Daniel Vetter
2022-01-21  9:09   ` Jani Nikula
2022-01-21  9:19     ` Lee Jones [this message]
2022-01-21  9:53       ` Helge Deller
2022-01-21 10:17         ` Lee Jones
2022-01-21  9:53       ` Daniel Vetter
2022-01-21 10:16         ` Lee Jones

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=Yep6te0wrK0ZQ8SB@google.com \
    --to=lee.jones@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jingoohan1@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).