linux-kernel - Re: linux-next: duplicate patches in the ktest tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230223162933.44766b78@gandalf.local.home>
Date:   Thu, 23 Feb 2023 16:29:33 -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 Thu, 23 Feb 2023 16:24:52 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Fri, 24 Feb 2023 08:17:08 +1100
> Stephen Rothwell <sfr@...b.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