From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Greg KH <greg@kroah.com>,
xen-devel@lists.xensource.com,
Greg Kroah-Hartman <gregkh@suse.de>,
virtualization@lists.osdl.org
Subject: Re: [PATCH] xen block: remove driver_data direct access of struct device
Date: Thu, 30 Apr 2009 16:25:36 -0700 [thread overview]
Message-ID: <49FA3370.7010802@goop.org> (raw)
In-Reply-To: <20090430224337.GP3036@sequoia.sous-sol.org>
Chris Wright wrote:
> * Greg KH (greg@kroah.com) wrote:
>
>> Thanks, will add it. Any objections for this to go through my
>> driver-core tree to Linus for 2.6.31?
>>
>
> None from me.
>
Fine by me.
Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
J
next prev parent reply other threads:[~2009-04-30 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 22:24 [PATCH] xen block: remove driver_data direct access of struct device Greg Kroah-Hartman
2009-04-30 22:35 ` Chris Wright
2009-04-30 22:37 ` Greg KH
2009-04-30 22:43 ` Chris Wright
2009-04-30 23:25 ` Jeremy Fitzhardinge [this message]
2009-04-30 23:38 ` Greg KH
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=49FA3370.7010802@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).