From: Steven Rostedt <rostedt@goodmis.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 ktest tree
Date: Thu, 23 Feb 2023 16:24:52 -0500 [thread overview]
Message-ID: <20230223162452.454a3fd6@gandalf.local.home> (raw)
In-Reply-To: <20230224081708.383a5e57@canb.auug.org.au>
On Fri, 24 Feb 2023 08:17:08 +1100
Stephen Rothwell <sfr@canb.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
next prev parent reply other threads:[~2023-02-23 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:17 Stephen Rothwell
2023-02-23 21:24 ` Steven Rostedt [this message]
2023-02-23 21:29 ` Steven Rostedt
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=20230223162452.454a3fd6@gandalf.local.home \
--to=rostedt@goodmis.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
all inboxes | Powered by JetHome®