public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org, apw@canonical.com,
	vkuznets@redhat.com
Subject: Re: [PATCH 1/6] Drivers: hv: vmbus: Perform device register in the per-channel work element
Date: Thu, 12 Mar 2015 11:44:21 +0100	[thread overview]
Message-ID: <20150312104421.GA11353@aepfle.de> (raw)
In-Reply-To: <1426125419-12571-1-git-send-email-kys@microsoft.com>

On Wed, Mar 11, K. Y. Srinivasan wrote:

> The current Linux 4.0 RC3 tree is broken and this patch fixes the problem.

This does not seem to apply to master. What it is based on?

checking file drivers/hv/channel_mgmt.c
Hunk #3 FAILED at 139.
Hunk #4 succeeded at 194 (offset -31 lines).
Hunk #5 succeeded at 303 (offset -18 lines).
Hunk #6 succeeded at 355 (offset -15 lines).
Hunk #7 FAILED at 471.
Hunk #8 FAILED at 634.
3 out of 8 hunks FAILED
checking file drivers/hv/connection.c
Hunk #1 succeeded at 263 (offset -7 lines).
Hunk #2 succeeded at 275 (offset -7 lines).
Hunk #3 succeeded at 287 (offset -7 lines).
checking file drivers/hv/hyperv_vmbus.h
Hunk #1 succeeded at 685 (offset -13 lines).

Olaf

  parent reply	other threads:[~2015-03-12 10:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  1:55 [PATCH 0/6] drivers: hv: vmbus: Some miscellaneous fixes for Linux 4.0 K. Y. Srinivasan
2015-03-12  1:56 ` [PATCH 1/6] Drivers: hv: vmbus: Perform device register in the per-channel work element K. Y. Srinivasan
2015-03-12  1:56   ` [PATCH 2/6] Drivers: hv: hv_balloon: keep locks balanced on add_memory() failure K. Y. Srinivasan
2015-03-12 10:45     ` Olaf Hering
2015-03-12 10:53       ` Vitaly Kuznetsov
2015-03-12 11:14         ` Olaf Hering
2015-03-12 11:41           ` Dan Carpenter
2015-03-12 12:44           ` KY Srinivasan
2015-03-12  1:56   ` [PATCH 3/6] Drivers: hv: hv_balloon: don't lose memory when onlining order is not natural K. Y. Srinivasan
2015-03-12  1:56   ` [PATCH 4/6] Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY K. Y. Srinivasan
2015-03-12  1:56   ` [PATCH 5/6] tools: hv: fcopy_daemon: support >2GB files for x86_32 guest K. Y. Srinivasan
2015-03-12  1:56   ` [PATCH 6/6] Drivers: hv: vmbus: Fix a bug in rescind processing in vmbus_close_internal() K. Y. Srinivasan
2015-03-12  9:02   ` [PATCH 1/6] Drivers: hv: vmbus: Perform device register in the per-channel work element Greg KH
2015-03-12  9:03     ` Greg KH
2015-03-12 13:12       ` KY Srinivasan
2015-03-12 13:28         ` Greg KH
2015-03-12 14:16           ` KY Srinivasan
2015-03-16 20:22             ` Greg KH
2015-03-16 21:09               ` KY Srinivasan
2015-03-17  4:50               ` KY Srinivasan
2015-03-12 10:44   ` Olaf Hering [this message]
2015-03-12 14:28     ` KY Srinivasan
2015-03-12 16:09       ` 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=20150312104421.GA11353@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    /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