All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Stefan Hajnoczi <stefanha@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] qtest: include system headers before user headers
Date: Fri, 14 Feb 2014 15:42:41 +0100	[thread overview]
Message-ID: <52FE2B61.8020902@suse.de> (raw)
In-Reply-To: <20140214143249.GG17391@stefanha-thinkpad.redhat.com>

Am 14.02.2014 15:32, schrieb Stefan Hajnoczi:
> On Sat, Feb 08, 2014 at 11:41:07AM +0100, Stefan Hajnoczi wrote:
>> It is dangerous to include user headers before system headers since user
>> macros can affect system headers.
>>
>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>>  tests/endianness-test.c |  2 +-
>>  tests/fw_cfg-test.c     |  7 +++----
>>  tests/i440fx-test.c     | 11 +++++------
>>  tests/m48t59-test.c     |  3 ++-
>>  tests/qom-test.c        |  3 ++-
>>  tests/rtc-test.c        |  5 +++--
>>  tests/tmp105-test.c     |  5 +++--
>>  7 files changed, 19 insertions(+), 17 deletions(-)
> 
> Ping?

I felt it wasn't long enough on the list before my v1 PULL. I can pick
it up for v2, now that no one has objected.

> Is anyone willing to be qtest maintainer, i.e. you understand qtest, can
> review patches, and will send pull requests?

I don't feel like the official qtest maintainer, but I care and am
actively working on it. I would consider it best to have individual
tests maintained by subsystem maintainers and only define a maintainer
for the core libqtest.c/qtest.c code.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-02-14 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 10:41 [Qemu-devel] [PATCH] qtest: include system headers before user headers Stefan Hajnoczi
2014-02-14 14:32 ` Stefan Hajnoczi
2014-02-14 14:42   ` Andreas Färber [this message]
2014-02-14 15:46     ` Stefan Hajnoczi

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=52FE2B61.8020902@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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 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.