All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Unable to parse -device drivers containing commas?
Date: Fri, 31 May 2013 08:56:08 +0100	[thread overview]
Message-ID: <51A85798.9000000@ilande.co.uk> (raw)
In-Reply-To: <51A7410F.6090700@redhat.com>

On 30/05/13 13:07, Eric Blake wrote:

>>   Is there a way of escaping the
>> commas on the command line so that it is possible to list properties for
>> drivers named in this way?
>
> Commas are escaped by doubling them.  Try ./qemu-system-sparc -device
> SUNW,,tcx,help
>
> That's the generic quoting we've used for escaping commas in all new
> command line options, although there may be some older options that
> still need to be taught to honor that escaping.

Hi Eric,

Yes that works absolutely fine here - thanks for the pointer!


Many thanks,

Mark.

      reply	other threads:[~2013-05-31  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 10:00 [Qemu-devel] Unable to parse -device drivers containing commas? Mark Cave-Ayland
2013-05-30 12:07 ` Eric Blake
2013-05-31  7:56   ` Mark Cave-Ayland [this message]

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=51A85798.9000000@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=eblake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.