qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	David Hildenbrand <david@redhat.com>
Cc: Farhan Ali <alifm@linux.vnet.ibm.com>,
	Jason J Herne <jjherne@linux.vnet.ibm.com>,
	Michael S Tsirkin <mst@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Pierre Morel <pmorel@linux.vnet.ibm.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Cleber Rosa <crosa@redhat.com>,
	Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] tests: Enable the drive_del test also on s390x
Date: Fri, 1 Sep 2017 12:39:49 +0200	[thread overview]
Message-ID: <96af6291-8427-89c8-c644-a3d82c3240c8@redhat.com> (raw)
In-Reply-To: <87o9qudbsk.fsf@dusky.pond.sub.org>

On 01.09.2017 11:10, Markus Armbruster wrote:
> David Hildenbrand <david@redhat.com> writes:
> 
>>>  static void test_drive_del_device_del(void)
>>>  {
>>> +    char *args;
>>> +
>>>      /* Start with a drive used by a device that unplugs instantaneously */
>>> -    qtest_start("-drive if=none,id=drive0,file=null-co://,format=raw"
>>> -                " -device virtio-scsi-pci"
>>> -                " -device scsi-hd,drive=drive0,id=dev0");
>>> +    args = g_strdup_printf("-drive if=none,id=drive0,file=null-co://,format=raw"
>>> +                           " -device virtio-scsi-%s"
>>> +                           " -device scsi-hd,drive=drive0,id=dev0",
>>
>> Would look better with the spaces at the end of the previous line (so
>> all "-device" are aligned), but just my taste.
> 
> The -device *are* aligned, but I get what you mean.
> 
> The advantage of leading rather than trailing space is that the
> intention "this is still the same string" is locally obvious both at the
> first part's end (no comma) and at the second part's beginning (leading
> space).

I don't mind either way, but in this case, I think I'd prefer to keep
the original formatting with the space at the beginning, for the
following two reasons:

- The first line is already hitting the 80 columns limit, and I want to
  avoid complaints from checkpatch.pl
- The original author formatted it that way.

 Thomas

  reply	other threads:[~2017-09-01 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 14:40 [Qemu-devel] [PATCH v2] tests: Enable the drive_del test also on s390x Thomas Huth
2017-08-31 15:36 ` David Hildenbrand
2017-09-01  9:10   ` Markus Armbruster
2017-09-01 10:39     ` Thomas Huth [this message]
2017-09-01 10:43       ` Cornelia Huck
2017-09-01 19:46       ` Eric Blake
2017-09-01 13:43 ` Cornelia Huck
2017-09-04 13:43   ` Cornelia Huck

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=96af6291-8427-89c8-c644-a3d82c3240c8@redhat.com \
    --to=thuth@redhat.com \
    --cc=alifm@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=crosa@redhat.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.vnet.ibm.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).