Linux-fbdev Archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, daniel.thompson@linaro.org,
	jingoohan1@gmail.com, deller@gmx.de,
	"Ricardo B. Marliere" <ricardo@marliere.net>
Subject: Re: [PATCH v2 1/2] video: backlight: make backlight_class constant
Date: Thu, 28 Mar 2024 12:09:07 +0000	[thread overview]
Message-ID: <20240328120907.GG13211@google.com> (raw)
In-Reply-To: <171162770830.1983471.4181539912129600848.b4-ty@kernel.org>

On Thu, 28 Mar 2024, Lee Jones wrote:

> On Thu, 28 Mar 2024 12:59:06 +0100, Greg Kroah-Hartman wrote:
> > Since commit 43a7206b0963 ("driver core: class: make class_register() take
> > a const *"), the driver core allows for struct class to be in read-only
> > memory, so move the backlight_class structure to be declared at build time
> > placing it into read-only memory, instead of having to be dynamically
> > allocated at boot time.
> > 
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/2] video: backlight: make backlight_class constant
>       commit: 6683414cff25dc5b6e7dfe9dadf42b718384c892
> [2/2] video: backlight: lcd: make lcd_class constant
>       commit: d51564f749fe4e4efd570b0591f2d23696c90cc7

I also added Daniel's r/b.

-- 
Lee Jones [李琼斯]

      reply	other threads:[~2024-03-28 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 11:59 [PATCH v2 1/2] video: backlight: make backlight_class constant Greg Kroah-Hartman
2024-03-28 11:59 ` [PATCH v2 2/2] video: backlight: lcd: make lcd_class constant Greg Kroah-Hartman
2024-03-28 12:08 ` [PATCH v2 1/2] video: backlight: make backlight_class constant Lee Jones
2024-03-28 12:09   ` Lee Jones [this message]

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=20240328120907.GG13211@google.com \
    --to=lee@kernel.org \
    --cc=daniel.thompson@linaro.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jingoohan1@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricardo@marliere.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).