All of lore.kernel.org
 help / color / mirror / Atom feed
From: KY Srinivasan <kys@microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: RE: [PATCH 1/1] Drivers: hv: vmbus: Fix a bug in getting ACPI specified resources
Date: Thu, 20 Feb 2014 23:46:29 +0000	[thread overview]
Message-ID: <a43362cb8dfc4c62934217628170751f@BY2PR03MB299.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20140220234702.GA28682@kroah.com>



> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Thursday, February 20, 2014 3:47 PM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org
> Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Fix a bug in getting ACPI specified
> resources
> 
> On Thu, Feb 20, 2014 at 03:45:12PM -0800, K. Y. Srinivasan wrote:
> > Fix a bug in the resource walking code.
> >
> > Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> > ---
> >  drivers/hv/vmbus_drv.c |    2 ++
> >  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> Fails to apply to my char-misc-next branch (if you want it in
> 3.14-final, that's where it belongs...):
> 	checking file drivers/hv/vmbus_drv.c
> 	Hunk #1 FAILED at 899.
> 	1 out of 1 hunk FAILED

I will rebase it send it to you shortly.

Thanks,

K. Y

  reply	other threads:[~2014-02-20 23:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 23:45 [PATCH 1/1] Drivers: hv: vmbus: Fix a bug in getting ACPI specified resources K. Y. Srinivasan
2014-02-20 23:06 ` Greg KH
2014-02-20 23:35   ` KY Srinivasan
2014-02-20 23:47 ` Greg KH
2014-02-20 23:46   ` KY Srinivasan [this message]
2014-02-21  0:19   ` KY Srinivasan
2014-02-21  1:00     ` KY Srinivasan
2014-02-21  2:21     ` Greg KH
2014-02-21  3:10       ` KY Srinivasan
2014-02-21  4:06 K. Y. 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=a43362cb8dfc4c62934217628170751f@BY2PR03MB299.namprd03.prod.outlook.com \
    --to=kys@microsoft.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.