mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Belisko Marek <marek.belisko@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: virtualization@lists.linux-foundation.org,
	devel@driverdev.osuosl.org, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
	Andi Kleen <andi@firstfloor.org>, Dave Jones <davej@redhat.com>
Subject: Re: [patch 00/54] [Announce] Microsoft Hyper-V drivers for Linux
Date: Tue, 21 Jul 2009 15:38:43 +0200	[thread overview]
Message-ID: <e7c6a05e0907210638g188c9eabie656d5c3fb1365b9@mail.gmail.com> (raw)
In-Reply-To: <200907211407.40229.arnd@arndb.de>

On Tue, Jul 21, 2009 at 2:07 PM, Arnd Bergmann<arnd@arndb.de> wrote:
> On Monday 20 July 2009, Greg KH wrote:
>> Anyway, I agree, for a "proper" review, I will show the final, cleaned
>> up version, like normal.  But we aren't there just yet, that is why this
>> code is going to live in the staging tree for a while.  Give us some
>> time to get it fixed up.
>
> I would find it helpful to have them in a git tree (or a branch) that
> I can pull, so I can look at both the original code and the cleaned up
> state.
You can find sources in linux-next tree in /drivers/staging/hv directory.
(git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git)
>
> Any reason why the patches are not yet in your staging.git?
>
>        Arnd <><
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
>

Marek

  reply	other threads:[~2009-07-21 13:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 16:00 Greg Kroah-Hartman
2009-07-20 16:28 ` Greg KH
2009-07-20 16:59   ` Dave Jones
2009-07-20 17:03     ` Greg KH
2009-07-20 17:22       ` Dave Jones
     [not found]       ` <871vob4047.fsf@basil.nowhere.org>
2009-07-20 19:57         ` Greg KH
2009-07-21 12:07           ` Arnd Bergmann
2009-07-21 13:38             ` Belisko Marek [this message]
2009-07-21 16:51             ` Greg KH
2009-07-20 17:09     ` Matthias Urlichs
2009-07-20 17:15       ` Dave Jones
2009-07-20 17:36         ` Greg KH
2009-07-20 21:24 ` Jan Engelhardt
2009-07-20 21:33   ` Greg KH
2009-07-21 11:06 ` Balbir Singh
2009-07-21 16:51   ` Greg KH
2009-07-21 18:00   ` Hank Janssen
2009-07-21 18:22     ` Balbir Singh

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=e7c6a05e0907210638g188c9eabie656d5c3fb1365b9@mail.gmail.com \
    --to=marek.belisko@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=arnd@arndb.de \
    --cc=davej@redhat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=virtualization@lists.osdl.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
all inboxes | Powered by JetHome®