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: <20150527150614.GB1090@kroah.com>
Date:	Wed, 27 May 2015 08:06:14 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	Vitaly Kuznetsov <vkuznets@...hat.com>,
	Radim Krčmář <rkrcmar@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH v2 0/2] Drivers: hv: vmbus: use
 cpu_hotplug_enable/disable for CPU offlining prevention

On Wed, May 27, 2015 at 02:37:14PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: Vitaly Kuznetsov [mailto:vkuznets@...hat.com]
> > Sent: Wednesday, May 27, 2015 2:15 AM
> > To: KY Srinivasan
> > Cc: devel@...uxdriverproject.org; Haiyang Zhang; linux-
> > kernel@...r.kernel.org; Dexuan Cui; Ingo Molnar; Paul E. McKenney; Rafael
> > J. Wysocki; Peter Zijlstra; Thomas Gleixner; Radim Krčmář
> > Subject: Re: [PATCH v2 0/2] Drivers: hv: vmbus: use
> > cpu_hotplug_enable/disable for CPU offlining prevention
> > 
> > KY Srinivasan <kys@...rosoft.com> writes:
> > 
> > >> -----Original Message-----
> > >> From: Vitaly Kuznetsov [mailto:vkuznets@...hat.com]
> > >> Sent: Thursday, May 21, 2015 9:22 AM
> > >> To: devel@...uxdriverproject.org
> > >> Cc: KY Srinivasan; Haiyang Zhang; linux-kernel@...r.kernel.org; Dexuan
> > Cui;
> > >> Ingo Molnar; Paul E. McKenney; Rafael J. Wysocki; Peter Zijlstra; Thomas
> > >> Gleixner; Radim Krčmář
> > >> Subject: [PATCH v2 0/2] Drivers: hv: vmbus: use
> > cpu_hotplug_enable/disable
> > >> for CPU offlining prevention
> > >>
> > >> Changes since v1:
> > >> - Make cpu_hotplug_disabled a counter [Radim Krčmář]
> > >>
> > >> Export cpu_hotplug_enable/cpu_hotplug_disable functions from cpu.c
> > and
> > >> use
> > >> them instead of altering smp_ops.cpu_disable in Hyper-V vmbus module.
> > >>
> > >> Vitaly Kuznetsov (2):
> > >>   cpu-hotplug: export cpu_hotplug_enable/cpu_hotplug_disable
> > >>   Drivers: hv: vmbus: use cpu_hotplug_enable/disable
> > >
> > > Vitaly,
> > >
> > > Since there is a cross tree dependency here, could you resubmit the vmbus
> > patch
> > > after the CPU hotplug patch has been committed.
> > 
> > I'm afraid it won't be committed without the second patch as without a
> > single user of cpu_hotplug_enable/cpu_hotplug_disable (among modules)
> > this patch doesn't make much sense. I would rather expect both of them
> > to go through Greg's tree but with proper sign-offs/reviewed-bys. And
> > of course this decision is up to tree maintainers, I'll resubmit the
> > vmbus patch in case CPU hotplug patch gets committed separately.
> 
> I had asked if Greg could take both the patches and I have not heard from him yet and I
> assumed that he would not.

Don't you love it when people ask you to do things, yet never even cc:
you on an email and still expect you to magically notice and respond to
them?

{sigh}

You got lucky here, I happened to notice this email, but I have no email
from you to me where you asked me to do anything.

As I told you before, you need to repackage up patches you want to have
applied and send them to me, that's the job of a subsystem maintainer,
you can't just "expect" someone else to magically notice them and apply
them for you.

greg k-h
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ