qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [RfC PATCH 0/2] usb: reorganize source files.
Date: Fri, 09 Mar 2012 07:50:46 +0100	[thread overview]
Message-ID: <4F59A846.9080300@redhat.com> (raw)
In-Reply-To: <4F5924C4.3020303@suse.de>

  Hi,

> For another, dev-foo.c is not natural English for a certain type of
> device - foo-dev.c would be better but I'd prefer without "dev", i.e.,
> hw/usb/{audio,ccid,...}.c. And then of course only devices should go
> into hw/.

I want a prefix because with prefixing you get the files nicely grouped
in directory listings, without creating another directory level, which
would IMHO be overkill for the number of files we have here.

'dev-*' is used for emulated usb devices (mouse, stick, ...), 'hcd-*' is
used for emulated usb host adapters (uhci, ehci, ...), 'host-*' is used
for host device pass-through code.

'dev-' isn't the greated pick as it is somewhat generic indeed.  I've
also considered 'emu-' (to contrast with host-*), but it has pretty much
the same issue.  Other suggestions?

cheers,
  Gerd

  reply	other threads:[~2012-03-09  6:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  9:16 [Qemu-devel] [RfC PATCH 0/2] usb: reorganize source files Gerd Hoffmann
2012-03-08  9:16 ` [Qemu-devel] [RfC PATCH 1/2] usb: the big rename Gerd Hoffmann
2012-03-08  9:37   ` Alon Levy
2012-03-09  8:34   ` Paolo Bonzini
2012-03-09  8:42     ` Gerd Hoffmann
2012-03-09  8:52       ` Paolo Bonzini
2012-03-09  9:26         ` Gerd Hoffmann
2012-03-08  9:16 ` [Qemu-devel] [RfC PATCH 2/2] usb: zap hw/ush-{ohic, uhci}.h + init wrappers Gerd Hoffmann
2012-03-08 21:29 ` [Qemu-devel] [RfC PATCH 0/2] usb: reorganize source files Andreas Färber
2012-03-09  6:50   ` Gerd Hoffmann [this message]
2012-03-09  8:35     ` Markus Armbruster
2012-03-09  8:46       ` Gerd Hoffmann
2012-03-09  8:37     ` Paolo Bonzini
2012-03-08 21:37 ` Anthony Liguori

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=4F59A846.9080300@redhat.com \
    --to=kraxel@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --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).