From: Stefan Weil <sw@weilnetz.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, imammedo@redhat.com
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] qemu-common: Declare qemu_irq earlier
Date: Fri, 24 Aug 2012 19:33:06 +0200 [thread overview]
Message-ID: <5037BAD2.5060909@weilnetz.de> (raw)
In-Reply-To: <CAJSP0QWSg9B2_H6QBtZHDsJQdeZL+oW=AK7aYZw_AzKnHZq9Vw@mail.gmail.com>
Am 24.08.2012 13:56, schrieb Stefan Hajnoczi:
> On Fri, Aug 24, 2012 at 12:06 PM, Peter Maydell
> <peter.maydell@linaro.org> wrote:
>> On 24 August 2012 11:54, Stefan Hajnoczi<stefanha@gmail.com> wrote:
>>> On Mon, Aug 20, 2012 at 06:45:00AM +0200, Stefan Weil wrote:
>>>> This allows using qemu_irq in the target specific cpu.h.
>>>>
>>>> Signed-off-by: Stefan Weil<sw@weilnetz.de>
>>>> ---
>>>> qemu-common.h | 3 ++-
>>>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>>
>>> I'm not sure if there's a reason why qemu_irq was previously hidden from
>>> cpu.h but the code change itself is fine and no one else has commented.
>>>
>>> Thanks, applied to the trivial patches tree:
>>> https://github.com/stefanha/qemu/commits/trivial-patches
>>
>> Consensus seemed to be that it was better to move qemu_irq
>> into hw/irq.h, as discussed in this mail thread:
>> http://lists.gnu.org/archive/html/qemu-devel/2012-08/msg03463.html
>> rather than just doing a move of the typedef within this header.
>
> Fine by me. I won't send a pull request with this patch yet.
>
> Stefan Weil: Are you happy to use the hw/irq.h patch instead of this?
>
> Stefan
Stefan H., that's OK.
Cheers,
Stefan
prev parent reply other threads:[~2012-08-24 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 4:45 [Qemu-devel] [PATCH] qemu-common: Declare qemu_irq earlier Stefan Weil
2012-08-24 10:54 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2012-08-24 11:06 ` Peter Maydell
2012-08-24 11:56 ` Stefan Hajnoczi
2012-08-24 17:33 ` Stefan Weil [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=5037BAD2.5060909@weilnetz.de \
--to=sw@weilnetz.de \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@gmail.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).