From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
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 tty tree
Date: Mon, 24 Feb 2025 07:14:13 +0100 [thread overview]
Message-ID: <2025022451-planner-motion-5d5b@gregkh> (raw)
In-Reply-To: <20250224155015.7790ed0f@canb.auug.org.au>
On Mon, Feb 24, 2025 at 03:50:15PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the tip tree as different commits
> (but the same patches):
>
> a2d1afe65a15 ("serial: xilinx_uartps: Use helper function hrtimer_update_function()")
> d2fa8e52cf91 ("serial: xilinx_uartps: Switch to use hrtimer_setup()")
> 7ba2facc3f91 ("serial: sh-sci: Switch to use hrtimer_setup()")
> afa51660033c ("serial: imx: Switch to use hrtimer_setup()")
> 8cb44188b986 ("serial: amba-pl011: Switch to use hrtimer_setup()")
> d45545c32904 ("serial: 8250: Switch to use hrtimer_setup()")
>
> These are commits
>
> eee00df8e1f1 ("serial: xilinx_uartps: Use helper function hrtimer_update_function()")
> 0852ca41ce1c ("serial: xilinx_uartps: Switch to use hrtimer_setup()")
> 4e1214969603 ("serial: sh-sci: Switch to use hrtimer_setup()")
> 721c5bf65a1d ("serial: imx: Switch to use hrtimer_setup()")
> c5f0fa1622f6 ("serial: amba-pl011: Switch to use hrtimer_setup()")
> 6bf9bb76b3af ("serial: 8250: Switch to use hrtimer_setup()")
>
> in the tip tree.
Yeah, sorry, my fault, I forgot to drop them. We'll just live with them
for now.
greg k-h
prev parent reply other threads:[~2025-02-24 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 4:50 linux-next: duplicate patches in the tty tree Stephen Rothwell
2025-02-24 6:14 ` Greg KH [this message]
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=2025022451-planner-motion-5d5b@gregkh \
--to=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.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 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.