All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Lee Jones <lee@kernel.org>, Jingoo Han <jingoohan1@gmail.com>,
	 Daniel Thompson <daniel.thompson@linaro.org>
Cc: Luca Weiss <luca@z3ntu.xyz>,
	dri-devel@lists.freedesktop.org,  linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH RESEND 4/4] backlight: mp3309c: Fully initialize backlight_properties during probe
Date: Fri, 23 Feb 2024 16:28:47 +0000	[thread overview]
Message-ID: <170870572786.1740438.15453067020985270956.b4-ty@kernel.org> (raw)
In-Reply-To: <20240220153532.76613-5-daniel.thompson@linaro.org>

On Tue, 20 Feb 2024 15:35:27 +0000, Daniel Thompson wrote:
> props is stack allocated and, although this driver initializes all the
> fields that are not "owned" by the framework, we'd still like to ensure
> it is zeroed to avoid problems from this driver if the fields change.
> 
> 

Applied, thanks!

[4/4] backlight: mp3309c: Fully initialize backlight_properties during probe
      commit: 50a2c0aee92699ed47076636b652f9d27a20fbef

--
Lee Jones [李琼斯]


  reply	other threads:[~2024-02-23 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 15:35 [PATCH RESEND 0/4] Ensure all backlight drivers zero the properties structure Daniel Thompson
2024-02-20 15:35 ` [PATCH RESEND 1/4] backlight: da9052: Fully initialize backlight_properties during probe Daniel Thompson
2024-02-20 15:35 ` [PATCH RESEND 2/4] backlight: lm3639: " Daniel Thompson
2024-02-20 15:35 ` [PATCH RESEND 3/4] backlight: lp8788: " Daniel Thompson
2024-02-20 15:35 ` [PATCH RESEND 4/4] backlight: mp3309c: " Daniel Thompson
2024-02-23 16:28   ` Lee Jones [this message]
2024-02-20 16:48 ` [PATCH RESEND 0/4] Ensure all backlight drivers zero the properties structure Luca Weiss
2024-02-23 16:31 ` Lee Jones
2024-02-29 17:39 ` (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=170870572786.1740438.15453067020985270956.b4-ty@kernel.org \
    --to=lee@kernel.org \
    --cc=daniel.thompson@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jingoohan1@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca@z3ntu.xyz \
    /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.