linux-kernel - Re: [RFC PATCH v2 0/5] allow overriding default preempt mode from command line

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201009132239.GP2628@hirez.programming.kicks-ass.net>
Date:   Fri, 9 Oct 2020 15:22:39 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Michal Hocko <mhocko@...e.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>, Mel Gorman <mgorman@...e.de>,
        Frederic Weisbecker <fweisbecker@...e.de>,
        Ingo Molnar <mingo@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2 0/5] allow overriding default preempt mode from
 command line

On Fri, Oct 09, 2020 at 03:03:44PM +0200, Michal Hocko wrote:
> On Fri 09-10-20 14:50:56, Peter Zijlstra wrote:
> > 
> > Can you please not thread the new series onto the old one? That's some
> > seriously annoying behaviour that I see more and more... It makes me
> > loose whole patch-sets.
> 
> Sure, no problem. This is not really unusual in mm and I personally
> prefer to have discussion in a single thread rather than separated in
> two or more. But I definitely do not insist of course. It is surprising
> that you are losing the whole patchset as the threading seems to be done
> properly. Mutt doesn't seem to have problems with that.

I often sort by thread and date and look at the recent most threads.
Mutt sorts threads by first post, not most recent post, hence the thread
is 'lost'.

> Anyway, let me know if I should repost.

I've already broken the thread (#), no need to repost.