public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamal Mostafa <kamal@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: luis.henriques@canonical.com, kamal.mostafa@canonical.com,
	sasha.levin@oracle.com, gregkh@linuxfoundation.org,
	nmeier@microsoft.com, fengguang.wu@intel.com, kys@microsoft.com,
	haiyangz@microsoft.com, devel@linuxdriverproject.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [v3.16.y-ckt][v3.18.y][v3.19.y-ckt][v4.0.y][PATCH 0/1][Hyper-V] Add support for VMBus panic notifier handler
Date: Wed, 17 Jun 2015 11:22:29 -0700	[thread overview]
Message-ID: <1434565349.2236.6.camel@fourier> (raw)
In-Reply-To: <cover.1434400846.git.joseph.salisbury@canonical.com>

On Tue, 2015-06-16 at 16:22 -0400, Joseph Salisbury wrote:
> Hello,
> 
> Please consider including upstream commits 96c1d0581d00f7abe033350edb021a9d947d8d81 and
> 5ef5b6927f14f29cacd78fa1fb861661a5367f13 in the next v3.16.y-ckt, v3.18.y, v3.19.y-ckt and v4.0.y releases.  
> They were included mainline as of v4.1-rc1.  They have been tested and confirmed to resolve
> http://bugs.launchpad.net/bugs/1463584 .
> 
> 
> commit 96c1d0581d00f7abe033350edb021a9d947d8d81
> Author: Nick Meier <nmeier@microsoft.com>
> Date:   Sat Feb 28 11:39:01 2015 -0800
> 
>     Drivers: hv: vmbus: Add support for VMBus panic notifier handler
> 
> commit 5ef5b6927f14f29cacd78fa1fb861661a5367f13
> Author: Nick Meier <nmeier@microsoft.com>
> Date:   Wed Mar 18 12:29:24 2015 -0700
> 
>     Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY
> 
> 
> Commit 96c1d05 does not cherry-pick cleanly, so I performed a backport, which is
> in email 1/1.

Thanks Joseph!  Queued up for 3.19-stable.

 -Kamal



      parent reply	other threads:[~2015-06-17 18:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 20:04 [3.13.y-ckt][PATCH 0/1][Hyper-V] Add support for VMBus panic notifier handler Joseph Salisbury
2015-06-16 20:04 ` [3.13.y-ckt][PATCH 1/1] Drivers: hv: vmbus: " Joseph Salisbury
     [not found] ` <cover.1434395983.git.joseph.salisbury@canonical.com>
2015-06-16 20:22   ` [v3.16.y-ckt][v3.18.y][v3.19.y-ckt][v4.0.y][PATCH 1/1]Drivers: " Joseph Salisbury
2015-06-27  0:47     ` Greg KH
2015-06-30 15:20       ` Kamal Mostafa
     [not found] ` <cover.1434486527.git.joseph.salisbury@canonical.com>
2015-06-16 20:31   ` [v3.14.y][PATCH 1/1] Drivers: " Joseph Salisbury
2015-06-16 20:39     ` Greg KH
2015-06-16 20:41 ` [3.13.y-ckt][PATCH 0/1][Hyper-V] " Greg KH
2015-06-16 20:49   ` Joseph Salisbury
2015-06-17 14:50 ` [v3.16.y-ckt][v3.18.y][v3.19.y-ckt][v4.0.y][PATCH " Luis Henriques
2015-06-17 18:22 ` Kamal Mostafa [this message]

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=1434565349.2236.6.camel@fourier \
    --to=kamal@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=kamal.mostafa@canonical.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=nmeier@microsoft.com \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.org \
    /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