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: <alpine.DEB.2.21.1807301411010.2518@nanos.tec.linutronix.de>
Date:   Mon, 30 Jul 2018 14:19:47 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Mukesh Ojha <mojha@...eaurora.org>
cc:     linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>,
        Lai Jiangshan <jiangshanlai@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        Brendan Jackman <brendan.jackman@....com>,
        Mathieu Malaterre <malat@...ian.org>, gkohli@...eaurora.org,
        neeraju@...eaurora.org
Subject: Re: [PATCH v2] cpu/hotplug: Fix cpuhp_step name for timers

Mukesh,

On Thu, 26 Jul 2018, Mukesh Ojha wrote:

> Hi All,
> 
> Can i get input on this ?

Sure.

> Thanks,
> Mukesh
> On 7/24/2018 8:17 PM, Mukesh Ojha wrote:

The input you get is that it's unprofessional to poke people after TWO days
about a patch which is purely cosmetic.

It's perfectly fine to send a reminder after a week for important changes
and after two for trivial cleanups like this. You really cannot expect that
maintainers and other developers permanentely sit there twiddling thumbs
and wait for new mail to arrive in order to reply immediately.

Thanks,

	tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ