From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Lee Jones <lee@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the backlight tree
Date: Fri, 6 Jan 2023 11:35:09 +1100 [thread overview]
Message-ID: <20230106113509.5c101b53@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
Hi all,
The following commits are also in the backlight-fixes tree as different
commits (but the same patches):
44bbdb7e3a67 ("backlight: ktd253: Switch to use dev_err_probe() helper")
c0e09423bbb4 ("dt-bindings: backlight: qcom-wled: Add PMI8950 compatible")
73516cbcf8d9 ("backlight: pwm_bl: Drop support for legacy PWM probing")
Forgot to push out an updated backlight-fixes tree?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-06 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 0:35 Stephen Rothwell [this message]
2023-01-06 9:25 ` linux-next: duplicate patches in the backlight tree Lee Jones
2023-01-06 9:31 ` Lee Jones
2023-01-06 11:59 ` Stephen Rothwell
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=20230106113509.5c101b53@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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