linux-kernel - Re: linux-next: duplicate patches in the backlight tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y7fqdX8FPEZW32sM@google.com>
Date:   Fri, 6 Jan 2023 09:31:33 +0000
From:   Lee Jones <lee@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the backlight tree

On Fri, 06 Jan 2023, Lee Jones wrote:

> On Fri, 06 Jan 2023, Stephen Rothwell wrote:
> 
> > 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?

What's the branch name that you're tracking?

> Don't think so?
> 
> 88603b6dc4194 (HEAD -> refs/heads/backlight-fixes, tag: \
>   refs/tags/v6.2-rc2, 					\
>   refs/remotes/mfd/mfd-fixes, 				\
>   refs/remotes/leds/for-leds-next, 			\
>   refs/remotes/backlight/backlight-fixes, 		\

Ah, wait!  This is the old naming scheme.

I assume, despite the message above, you're tracking
'for-backlight-fixes', right?

>   refs/heads/mfd-fixes, 				\
>   refs/heads/for-leds-next) 				\
>     Linux 6.2-rc2

-- 
Lee Jones [李琼斯]