qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Otubo <otubo@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	mst@redhat.com, qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	Alexander Graf <agraf@suse.de>,
	qemu-ppc@nongnu.org, pbonzini@redhat.com,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] dma/i82374: avoid double creation of i82374 device
Date: Thu, 7 Sep 2017 10:38:55 +0200	[thread overview]
Message-ID: <20170907083855.GC2441@vader> (raw)
In-Reply-To: <20170902091520.bxecfhisvy46o4cb@aurel32.net>

On Sat, Sep 02, 2017 at 11:15:20AM +0200, Aurelien Jarno wrote:
> On 2017-09-01 11:30, Eduardo Habkost wrote:
> > i82374 is compiled in only on ppc and sh4, so I'm CCing the
> > maintainers for those architectures.
> 
> The i82374 device is not useful nor usable on SH4. It has just been
> added in commit 85d3846a39 to be able to run the tests.
> 
> Aurelien
> 

Any word from the ppc guys?

-- 
Eduardo Otubo
Senior Software Engineer @ RedHat

  reply	other threads:[~2017-09-07  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 11:03 [Qemu-devel] [PATCH] dma/i82374: avoid double creation of i82374 device Eduardo Otubo
2017-09-01 14:30 ` Eduardo Habkost
2017-09-01 15:34   ` Markus Armbruster
2017-09-01 15:44     ` Eduardo Habkost
2017-09-07  8:38       ` [Qemu-devel] [Qemu-trivial] " Eduardo Otubo
2017-09-09 21:52         ` Eduardo Habkost
2017-09-02  9:15   ` [Qemu-devel] " Aurelien Jarno
2017-09-07  8:38     ` Eduardo Otubo [this message]
2017-09-07 16:05     ` Paolo Bonzini
2017-09-08  7:57       ` [Qemu-devel] [Qemu-trivial] " Eduardo Otubo
  -- strict thread matches above, loose matches on Subject: below --
2017-09-15  9:06 [Qemu-devel] " Eduardo Otubo
2017-09-15  9:26 ` [Qemu-devel] [Qemu-trivial] " Eduardo Otubo

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=20170907083855.GC2441@vader \
    --to=otubo@redhat.com \
    --cc=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-trivial@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).