From: Lee Jones <lee@kernel.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: daniel.thompson@linaro.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-kernel@vger.kernel.org, geert+renesas@glider.be,
linux-sh@vger.kernel.org, jingoohan1@gmail.com, deller@gmx.de,
linux-staging@lists.linux.dev, javierm@redhat.com,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
michael.j.ruhl@intel.com, stable@vger.kernel.org,
linux-omap@vger.kernel.org, sam@ravnborg.org,
dan.carpenter@linaro.org
Subject: Re: [PATCH v3 01/38] backlight/bd6107: Compare against struct fb_info.device
Date: Mon, 19 Jun 2023 09:31:24 +0100 [thread overview]
Message-ID: <20230619083124.GO3635807@google.com> (raw)
In-Reply-To: <9f74b8de-9a1b-2547-5eab-d4b4349a6a81@suse.de>
On Fri, 16 Jun 2023, Thomas Zimmermann wrote:
> Hi Lee
>
> Am 14.06.23 um 16:13 schrieb Thomas Zimmermann:
> [...]
> > > Can the Backlight patches be applied without the others and visa versa?
> >
> > Unfortunately not. The rest of the series requires the backlight patches.
>
> Are you OK with the patches going through drm?
Shouldn't be an issue.
Please ensure my Ack is added to each patch, even if you have to RESEND.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-06-19 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230613110953.24176-1-tzimmermann@suse.de>
2023-06-13 11:06 ` [PATCH v3 01/38] backlight/bd6107: Compare against struct fb_info.device Thomas Zimmermann
2023-06-14 13:51 ` Lee Jones
2023-06-14 14:13 ` Thomas Zimmermann
2023-06-16 14:37 ` Thomas Zimmermann
2023-06-19 8:31 ` Lee Jones [this message]
2023-06-19 8:42 ` Thomas Zimmermann
2023-06-13 11:06 ` [PATCH v3 03/38] backlight/gpio_backlight: " Thomas Zimmermann
2023-06-13 11:06 ` [PATCH v3 05/38] backlight/lv5207lp: " Thomas Zimmermann
2023-06-13 11:06 ` [PATCH v3 14/38] fbdev/ep93xx-fb: Do not assign to struct fb_info.dev Thomas Zimmermann
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=20230619083124.GO3635807@google.com \
--to=lee@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=javierm@redhat.com \
--cc=jingoohan1@gmail.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=michael.j.ruhl@intel.com \
--cc=sam@ravnborg.org \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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).