linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: "olaf@aepfle.de" <olaf@aepfle.de>, Jiri Kosina <jkosina@suse.cz>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"James.Bottomley@HansenPartnership.com" 
	<James.Bottomley@HansenPartnership.com>,
	"apw@canonical.com" <apw@canonical.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH 6/6] Drivers: hv: Execute shutdown in a thread context
Date: Fri, 1 Mar 2013 08:11:24 -0800	[thread overview]
Message-ID: <20130301161124.GA3969@kroah.com> (raw)
In-Reply-To: <524a403348d240a8b24db0177e7aaecd@SN2PR03MB061.namprd03.prod.outlook.com>

On Fri, Mar 01, 2013 at 03:15:58PM +0000, KY Srinivasan wrote:
> > > > > Execute the shutdown code in a thread context. With recent changes made
> > > > the
> > > > > shutdown code, shutdown code cannot be invoked from an interrupt
> > context.
> > > > >
> > > > > Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> > > > > Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
> > > > > ---
> > > > >  drivers/hv/hv_util.c |   12 +++++++++++-
> > > > >  1 files changed, 11 insertions(+), 1 deletions(-)
> > > > >
> > > > > diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
> > > > > index 8b7868a..aceb67f 100644
> > > > > --- a/drivers/hv/hv_util.c
> > > > > +++ b/drivers/hv/hv_util.c
> > > > > @@ -49,6 +49,16 @@ static struct hv_util_service util_kvp = {
> > > > >  	.util_deinit = hv_kvp_deinit,
> > > > >  };
> > > > >
> > > > > +static void perform_shutdown(struct work_struct *dummy)
> > > > > +{
> > > > > +		orderly_poweroff(true);
> > > > > +}
> > > >
> > > > Is there any particular reason for this kind of crazy indentation?
> > > I don't know how this extra tab crept through! Greg, if you want I can resend
> > > this patch minus the extra tab. Let me know.
> > 
> > I'll edit it by hand, but someone owes me a beer for it...  :)
> 
> Greg,
> 
> You have already applied this. There has been some customer request for getting this
> patch into 3.7 (3.7 is where the Hyper-V shutdown code ceased to work because of 
> some other patches unrelated to Hyper-V that went in). What is the process for requesting
> that this patch be applied all the way back to 3.7.

You have read the file, Documentation/stable_kernel_rules.txt, right?

But please remember, the 3.7 kernel is now end-of-life, as of the 3.7.10
kernel release, so even if this was a bug fix that was applicable to
stable kernels, it would be impossible to get it into the 3.7.y
releases, without going back in time.

sorry,

greg k-h

  reply	other threads:[~2013-03-01 16:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  1:42 [PATCH 0/6] Drivers: hv: Consolidate GUID definitions K. Y. Srinivasan
2013-01-24  1:42 ` [PATCH 1/6] Drivers: hv: vmbus: Consolidate all offer GUID definitions in hyperv.h K. Y. Srinivasan
2013-01-24  1:42   ` [PATCH 2/6] Drivers: hv: Use consolidated GUID definitions K. Y. Srinivasan
2013-01-24  1:42   ` [PATCH 3/6] Drivers: net: hyperv: Use the consolidated GUID definition K. Y. Srinivasan
2013-01-24  1:42   ` [PATCH 4/6] Drivers: scsi: storvsc: " K. Y. Srinivasan
2013-01-24  1:42   ` [PATCH 5/6] Drivers: hid: hid-hyperv: Use consolidated GUID definitions K. Y. Srinivasan
2013-01-24 10:11     ` Jiri Kosina
2013-01-24 14:51       ` Greg KH
2013-01-24  1:42   ` [PATCH 6/6] Drivers: hv: Execute shutdown in a thread context K. Y. Srinivasan
2013-01-24 10:09     ` Jiri Kosina
2013-01-24 17:06       ` KY Srinivasan
2013-01-24 17:17         ` gregkh
2013-01-24 17:23           ` KY Srinivasan
2013-02-09  0:31           ` KY Srinivasan
2013-02-09  0:44             ` gregkh
2013-02-09  0:55               ` KY Srinivasan
2013-03-01 15:15           ` KY Srinivasan
2013-03-01 16:11             ` gregkh [this message]
2013-03-01 18:40               ` KY Srinivasan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130301161124.GA3969@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=devel@linuxdriverproject.org \
    --cc=jasowang@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).