[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230223162452.454a3fd6@gandalf.local.home>
Date: Thu, 23 Feb 2023 16:24:52 -0500
From: Steven Rostedt <rostedt@...dmis.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 ktest tree
On Fri, 24 Feb 2023 08:17:08 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> bbf45b2ab467 ("ktest: Restore stty setting at first in dodie")
> aa9aba938288 ("ktest.pl: Add RUN_TIMEOUT option with default unlimited")
> 5aa3b79933de ("ktest.pl: Give back console on Ctrt^C on monitor")
> fa77cb30e4a0 ("ktest.pl: Fix missing "end_monitor" when machine check fails")
>
> These are commits
>
> 7dc8e24f0e09 ("ktest: Restore stty setting at first in dodie")
> 4e7d2a8f0b52 ("ktest.pl: Add RUN_TIMEOUT option with default unlimited")
> 83d29d439cd3 ("ktest.pl: Give back console on Ctrt^C on monitor")
> e8bf9b98d40d ("ktest.pl: Fix missing "end_monitor" when machine check fails")
>
> in Linus' tree.
>
Ah sorry. When I was doing my pull request for Linus, I realized I
accidentally had a commit that wasn't to go upstream. I rebased to remove
it, but never updated my for-next branch.
Doing that now.
-- Steve
Powered by blists - more mailing lists