From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Paul Brook <paul@codesourcery.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Meador Inge <meadori@codesourcery.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v1 1/1] m68k: Return semihosting errno values correctly
Date: Tue, 27 Mar 2012 17:51:54 +0200 [thread overview]
Message-ID: <4F71E21A.7010009@suse.de> (raw)
In-Reply-To: <CAFEAcA8R+J+DeN7V_6bVHhh3kYprA8EKWJXEzfDp7iWjWzYLqQ@mail.gmail.com>
Am 27.03.2012 17:43, schrieb Peter Maydell:
> This patch is simple enough (and m68k unmaintained enough)
> that it could reasonably go through qemu-trivial I think.
This one's a Mentor-internal issue though - Paul, are you planning to
handle (your colleague's) m68k patches? Or should we downgrade m68k to
S: Orphan and handle them through some other to be defined way?
I'm asking because I have m68k QOM'ification in the queue and Anthony
has set out not to apply patches for which a submaintainer is defined.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Paul Brook <paul@codesourcery.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Meador Inge <meadori@codesourcery.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] m68k: Return semihosting errno values correctly
Date: Tue, 27 Mar 2012 17:51:54 +0200 [thread overview]
Message-ID: <4F71E21A.7010009@suse.de> (raw)
In-Reply-To: <CAFEAcA8R+J+DeN7V_6bVHhh3kYprA8EKWJXEzfDp7iWjWzYLqQ@mail.gmail.com>
Am 27.03.2012 17:43, schrieb Peter Maydell:
> This patch is simple enough (and m68k unmaintained enough)
> that it could reasonably go through qemu-trivial I think.
This one's a Mentor-internal issue though - Paul, are you planning to
handle (your colleague's) m68k patches? Or should we downgrade m68k to
S: Orphan and handle them through some other to be defined way?
I'm asking because I have m68k QOM'ification in the queue and Anthony
has set out not to apply patches for which a submaintainer is defined.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-27 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 22:18 [Qemu-devel] [PATCH v1 1/1] m68k: Return semihosting errno values correctly Meador Inge
2012-02-24 22:53 ` Andreas Färber
2012-03-27 15:07 ` Meador Inge
2012-03-27 15:43 ` [Qemu-trivial] " Peter Maydell
2012-03-27 15:43 ` Peter Maydell
2012-03-27 15:51 ` Andreas Färber [this message]
2012-03-27 15:51 ` Andreas Färber
2012-10-29 9:42 ` [Qemu-trivial] " Peter Maydell
2012-10-29 9:42 ` Peter Maydell
2012-10-29 10:03 ` [Qemu-trivial] " Stefan Hajnoczi
2012-10-29 10:03 ` [Qemu-devel] [Qemu-trivial] " 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=4F71E21A.7010009@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=meadori@codesourcery.com \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 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.