linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Lee Jones <lee@kernel.org>
Cc: linux@treblig.org, jingoohan1@gmail.com, hdegoede@redhat.com,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backlight: Remove notifier
Date: Wed, 9 Oct 2024 14:47:10 +0100	[thread overview]
Message-ID: <20241009134710.GA16179@aspen.lan> (raw)
In-Reply-To: <20241009102230.GC276481@google.com>

On Wed, Oct 09, 2024 at 11:22:30AM +0100, Lee Jones wrote:
> On Tue, 24 Sep 2024, Simona Vetter wrote:
>
> > On Fri, Sep 20, 2024 at 12:27:58AM +0100, linux@treblig.org wrote:
> > > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> > >
> > > backlight_register_notifier and backlight_unregister_notifier have
> > > been unused since
> > >   commit 6cb634d0dc85 ("ACPI: video: Remove code to unregister acpi_video
> > > backlight when a native backlight registers")
> > >
> > > With those not being called, it means that the backlight_notifier
> > > list is always empty.
> > >
> > > Remove the functions, the list itself and the enum used in the
> > > notifications.
> > >
> > > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> >
> > Reviewed-by: Simona Vetter <simona.vetter@ffwll.ch>
> >
> > I think Lee Jones or Daniel Thompson will pick this up.
>
> I will pick this up with Daniel's review.

Thanks for the patch... sorry for the delay. I just bumped this up my
TODO list a little ;-)

Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>


Daniel.

  reply	other threads:[~2024-10-09 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 23:27 [PATCH] backlight: Remove notifier linux
2024-09-24 11:21 ` Simona Vetter
2024-10-09 10:22   ` Lee Jones
2024-10-09 13:47     ` Daniel Thompson [this message]
2024-10-09 14:43 ` (subset) " 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=20241009134710.GA16179@aspen.lan \
    --to=daniel.thompson@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=jingoohan1@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.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).