From: Greg KH <greg@kroah.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Hank Janssen <hjanssen@microsoft.com>,
"'gregkh@suse.de'" <gregkh@suse.de>
Subject: Re: [PATCH 1/1] Stage: hv: Rename struct device_context and re-arrange the fields inside (re-formatted)
Date: Wed, 17 Feb 2010 15:52:23 -0800 [thread overview]
Message-ID: <20100217235223.GG12197@kroah.com> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF725A908A11@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Wed, Feb 17, 2010 at 08:58:47PM +0000, Haiyang Zhang wrote:
> From: Haiyang Zhang <haiyangz@microsoft.com>
>
> Rename struct device_context and re-arrange the fields inside.
> Rename struct device_context to struct vm_device, and move
> struct device field to the end according to Document/driver-model standard.
Ok, I fixed the patch up, but it looks like you did not make this
against the linux-next tree, but against Linus's tree, right? The code
has changed since Linus's tree a bit in places (dead code was removed),
and it conflicted with this patch.
Next time please be more careful.
thanks,
greg k-h
next prev parent reply other threads:[~2010-02-18 0:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:58 Haiyang Zhang
2010-02-17 21:05 ` Greg KH
2010-02-17 23:50 ` Greg KH
2010-02-17 23:52 ` Greg KH [this message]
2010-02-18 15:51 ` Haiyang Zhang
2010-03-03 16:42 ` Ringbuffer usage in Linux Hyper-V drivers Hank Janssen
2010-03-03 17:49 ` Jeremy Fitzhardinge
2010-03-03 23:39 ` Greg KH
2010-03-04 17:46 ` [PATCH 1/1] Stage: hv: Remove Ringbuffer from TODO line Hank Janssen
2010-03-04 17:48 ` [PATCH 1/1] Stage: hv: Corrected all header comments to follow kernel-doc format Hank Janssen
2010-03-04 17:55 ` Joe Perches
2010-03-04 18:03 ` Randy Dunlap
2010-03-04 18:11 ` Hank Janssen
2010-03-04 22:11 ` [PATCH 1/1] Stage: hv: Corrected all header comments to follow kernel-doc format-CORRECTED Hank Janssen
2010-03-04 22:37 ` Randy Dunlap
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=20100217235223.GG12197@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome