From: Lee Jones <lee@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Stephen Kitt <steve@sk2.org>, Jingoo Han <jingoohan1@gmail.com>,
linux-fbdev@vger.kernel.org, Helge Deller <deller@gmx.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH RESEND 1/4] backlight: aat2870: Use backlight helper
Date: Mon, 9 Jan 2023 16:35:15 +0000 [thread overview]
Message-ID: <Y7xCQ68aRTK19eRg@google.com> (raw)
In-Reply-To: <Y7vsAdMqGNgYS/m9@aspen.lan>
On Mon, 09 Jan 2023, Daniel Thompson wrote:
> On Fri, Jan 06, 2023 at 06:43:36PM +0100, Daniel Vetter wrote:
> > On Fri, Jan 06, 2023 at 05:48:52PM +0100, Stephen Kitt wrote:
> > > Instead of retrieving the backlight brightness in struct
> > > backlight_properties manually, and then checking whether the backlight
> > > should be on at all, use backlight_get_brightness() which does all
> > > this and insulates this from future changes.
> > >
> > > Signed-off-by: Stephen Kitt <steve@sk2.org>
> >
> > Lee/Daniel, will you pick these up, or should I smash them all into
> > drm-misc-next for 6.3?
>
> Outside of holiday, Lee usually hoovers up the backlight patches (and
> negotiates about who merges what).
Right, I'll collect these into the Backlight tree if there aren't any
build deps involved. If there are, we'll need to devise a strategy
that will likely involve immutable branches.
--
Lee Jones [李琼斯]
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: linux-fbdev@vger.kernel.org, Stephen Kitt <steve@sk2.org>,
Jingoo Han <jingoohan1@gmail.com>, Helge Deller <deller@gmx.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH RESEND 1/4] backlight: aat2870: Use backlight helper
Date: Mon, 9 Jan 2023 16:35:15 +0000 [thread overview]
Message-ID: <Y7xCQ68aRTK19eRg@google.com> (raw)
In-Reply-To: <Y7vsAdMqGNgYS/m9@aspen.lan>
On Mon, 09 Jan 2023, Daniel Thompson wrote:
> On Fri, Jan 06, 2023 at 06:43:36PM +0100, Daniel Vetter wrote:
> > On Fri, Jan 06, 2023 at 05:48:52PM +0100, Stephen Kitt wrote:
> > > Instead of retrieving the backlight brightness in struct
> > > backlight_properties manually, and then checking whether the backlight
> > > should be on at all, use backlight_get_brightness() which does all
> > > this and insulates this from future changes.
> > >
> > > Signed-off-by: Stephen Kitt <steve@sk2.org>
> >
> > Lee/Daniel, will you pick these up, or should I smash them all into
> > drm-misc-next for 6.3?
>
> Outside of holiday, Lee usually hoovers up the backlight patches (and
> negotiates about who merges what).
Right, I'll collect these into the Backlight tree if there aren't any
build deps involved. If there are, we'll need to devise a strategy
that will likely involve immutable branches.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-01-09 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:48 [PATCH RESEND 1/4] backlight: aat2870: Use backlight helper Stephen Kitt
2023-01-06 16:48 ` Stephen Kitt
2023-01-06 17:43 ` Daniel Vetter
2023-01-06 17:43 ` Daniel Vetter
2023-01-06 20:26 ` Stephen Kitt
2023-01-06 20:26 ` Stephen Kitt
2023-01-09 10:27 ` Daniel Thompson
2023-01-09 16:35 ` Lee Jones [this message]
2023-01-09 16:35 ` Lee Jones
2023-01-06 17:44 ` Sam Ravnborg
2023-01-06 17:44 ` Sam Ravnborg
2023-01-09 10:16 ` Daniel Thompson
2023-01-09 10:16 ` Daniel Thompson
2023-01-19 21:41 ` Lee Jones
2023-01-19 21:41 ` 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=Y7xCQ68aRTK19eRg@google.com \
--to=lee@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=steve@sk2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.