From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: qemu-ppc@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [PATCH v3 1/2] MAINTAINERS: Add missing m48t59 files to the PReP section
Date: Mon, 20 Jan 2020 20:10:02 +0100 [thread overview]
Message-ID: <d566490e-512c-527c-4b7e-b6e20cf790f0@redhat.com> (raw)
In-Reply-To: <f5181fa3-e830-7d04-1f4e-0673d2202eec@redhat.com>
On 1/20/20 6:53 AM, Thomas Huth wrote:
> On 17/01/2020 17.58, Philippe Mathieu-Daudé wrote:
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> MAINTAINERS | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 4b425d030d..c162145bd0 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1084,6 +1084,8 @@ F: hw/pci-host/prep.[hc]
>> F: hw/isa/i82378.c
>> F: hw/isa/pc87312.c
>> F: hw/dma/i82374.c
>> +F: hw/rtc/m48t59.c
>> +F: hw/rtc/m48t59-internal.h
>> F: hw/rtc/m48t59-isa.c
>> F: include/hw/isa/pc87312.h
>> F: include/hw/rtc/m48t59.h
>
> Why only PReP? The device seems also to be used by Sparc machines...?
Indeed, and also the PowerPC405 evaluation boards, so I'll simply drop
this patch.
next prev parent reply other threads:[~2020-01-20 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 16:58 [PATCH v3 0/2] hw/timer/m48t59: Convert to trace events Philippe Mathieu-Daudé
2020-01-17 16:58 ` [PATCH v3 1/2] MAINTAINERS: Add missing m48t59 files to the PReP section Philippe Mathieu-Daudé
2020-01-20 5:53 ` Thomas Huth
2020-01-20 19:10 ` Philippe Mathieu-Daudé [this message]
2020-01-20 5:54 ` Thomas Huth
2020-01-17 16:58 ` [PATCH v3 2/2] hw/timer/m48t59: Convert debug printf()s to trace events Philippe Mathieu-Daudé
2020-01-20 19:12 ` Philippe Mathieu-Daudé
2020-02-06 9:51 ` Laurent Vivier
2020-01-18 8:45 ` [PATCH v3 0/2] hw/timer/m48t59: Convert " Hervé Poussineau
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=d566490e-512c-527c-4b7e-b6e20cf790f0@redhat.com \
--to=philmd@redhat.com \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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).