linux-kernel - Re: [PATCH v2] sched: Micro optimization in pick_next_task() and in check_preempt

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20191219112214.37f1f0af@gandalf.local.home>
Date:   Thu, 19 Dec 2019 11:22:14 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Kirill Tkhai <ktkhai@...tuozzo.com>
Cc:     Peter Zijlstra <peterz@...radead.org>, mingo@...hat.com,
        juri.lelli@...hat.com, vincent.guittot@...aro.org,
        dietmar.eggemann@....com, bsegall@...gle.com, mgorman@...e.de,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] sched: Micro optimization in pick_next_task() and in
 check_preempt_curr()

On Thu, 19 Dec 2019 19:08:05 +0300
Kirill Tkhai <ktkhai@...tuozzo.com> wrote:

> Should I resend this as two patches, with your changes in a separate?

You don't have to, you can include multiple SOBs if a patch was written
by two people.

But perhaps it will better to do so, that way people will know who to
blame when the linker breaks ;-)

I'll send you a patch that you can apply just before your change. That
may be the cleanest way.

-- Steve