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:29:33 -0500 [thread overview]
Message-ID: <20230223162933.44766b78@gandalf.local.home> (raw)
In-Reply-To: <20230223162452.454a3fd6@gandalf.local.home>
On Thu, 23 Feb 2023 16:24:52 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 24 Feb 2023 08:17:08 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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.
The commit message even had:
ktest.pl: Process variables within variables
Allow a variable to contain another variable. This will allow the
${shell <command>} to have its command include variables.
[ When I remember the use case for this, I'll send out the real patch ]
Which is what reminded me that it wasn't suppose to have been in for-next
to begin with.
>
> Doing that now.
Done.
-- Steve
prev parent reply other threads:[~2023-02-23 21:30 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
2023-02-23 21:29 ` Steven Rostedt [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=20230223162933.44766b78@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®