[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1506251652300.4037@nanos>
Date: Thu, 25 Jun 2015 16:57:59 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
cc: devel@...uxdriverproject.org,
"K. Y. Srinivasan" <kys@...rosoft.com>,
linux-kernel@...r.kernel.org, Dexuan Cui <decui@...rosoft.com>,
Ingo Molnar <mingo@...nel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Radim Krčmář <rkrcmar@...hat.com>,
gregkh@...uxfoundation.org
Subject: Re: [PATCH v5 1/2] cpu-hotplug: export
cpu_hotplug_enable/cpu_hotplug_disable
On Thu, 25 Jun 2015, Vitaly Kuznetsov wrote:
> Loaded Hyper-V module will use these functions to disable CPU hotplug
> under certain circumstances. Convert cpu_hotplug_disabled to a counter
> (protected by cpu_add_remove_lock) to support e.g. disable -> disable ->
> enable call sequences.
This changelog including the subject line still sucks.
Q: How is the counter change related subject line?
A: Not at all.
Q: Why do we need to change this to a counter?
A: Because
Q: What problem is being solved?
A: Dunno
Q: Why do we need the export?
A: HyperV having certain circumstances
Summary: The changelog is useless
The patch wants to be split in two parts:
1) Make the counter change and explain why the current mode is not
sufficient and what kind of problem can be solved
2) Export the functions with a proper explanation why.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists