From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the backlight tree
Date: Fri, 6 Jan 2023 09:31:33 +0000 [thread overview]
Message-ID: <Y7fqdX8FPEZW32sM@google.com> (raw)
In-Reply-To: <Y7fo+tMnkSndJNXV@google.com>
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 [李琼斯]
next prev parent reply other threads:[~2023-01-06 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 0:35 linux-next: duplicate patches in the backlight tree Stephen Rothwell
2023-01-06 9:25 ` Lee Jones
2023-01-06 9:31 ` Lee Jones [this message]
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=Y7fqdX8FPEZW32sM@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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