From: "Andreas Färber" <afaerber@suse.de>
To: Keith Busch <keith.busch@gmail.com>
Cc: Keith Busch <keith.busch@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Hannes Reinecke <hare@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] NVMe: Initial commit to add an NVM Express device
Date: Sat, 08 Dec 2012 21:59:35 +0100 [thread overview]
Message-ID: <50C3AA37.9000308@suse.de> (raw)
In-Reply-To: <CAOSXXT6M1++X+68OOZy=y-wFxYhKwutEC_Pf4esg1C_kFZHD0w@mail.gmail.com>
Am 08.12.2012 20:20, schrieb Keith Busch:
> On Sat, Dec 8, 2012 at 10:59 AM, Andreas Färber <afaerber@suse.de> wrote:
>> Generally we encourage people to upstream their devices, given they are
>> sufficiently isolated and/or maintainable.
>
> Yes, that makes sense and have been doing that. We maintain an
> upstream repo, but needed to merge with a more recent qemu release for
> some critical updates and many api's changed from where we were.
> Merging was just a small matter of coding, but I thought it might be
> easier to keep up with the latest and greatest if it was part of it,
> if that's ok to do. [...]
With upstream I was referring to qemu.git, i.e. you are on the right
track with this patch in relation to your downstream repository. The
only bottleneck you will experience is reviewers and committers for a
device/technology that not everyone uses.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-12-08 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 0:05 [Qemu-devel] [PATCH] NVMe: Initial commit to add an NVM Express device Keith Busch
2012-12-08 7:38 ` Stefan Weil
2012-12-08 7:52 ` Stefan Weil
2012-12-08 17:59 ` Andreas Färber
2012-12-08 19:20 ` Keith Busch
2012-12-08 20:59 ` Andreas Färber [this message]
2012-12-10 12:36 ` Kevin Wolf
2012-12-10 14:11 ` Stefan Hajnoczi
2012-12-10 16:28 ` Busch, Keith
2012-12-13 0:13 ` Busch, Keith
2012-12-13 9:12 ` Kevin Wolf
2012-12-13 9:34 ` Paolo Bonzini
2012-12-13 9:33 ` Paolo Bonzini
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=50C3AA37.9000308@suse.de \
--to=afaerber@suse.de \
--cc=hare@suse.de \
--cc=keith.busch@gmail.com \
--cc=keith.busch@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).