From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Fam Zheng" <fam@euphon.net>,
qemu-trivial@nongnu.org, "Magnus Damm" <magnus.damm@gmail.com>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH 0/5] hw/sh4: current patch queue
Date: Mon, 01 Jun 2020 11:32:35 +0100 [thread overview]
Message-ID: <87tuzv6pq4.fsf@linaro.org> (raw)
In-Reply-To: <8279188f-f6a7-4d0e-50d9-de1c66619e50@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> On 5/31/20 12:18 PM, Alex Bennée wrote:
>>
>> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>>
>>> Hi,
>>>
>>> As there is no SH4 active maintainer, I gathered various
>>> patches in a single series, in case someone is willing to
>>> apply them.
>>
>> I'm sure you you could put yourself down as an "Odd Fixes" maintainer
>> and put together a PR if you want?
>
> Odd Fixes: It has a maintainer but they don't have time to do
> much other than throw the odd patch in.
>
> OK 'Odd Fixes' matches what I can offer as a hobbyist.
> I'm happy to help avoiding this code to bitrot, as long as I don't get
> the same pressure imposed on other targets.
Yeah Odd Fixes doesn't imply anything other than at least some might
look at it. It's easier that convincing someone else who cares even less
to put it in a PR for you ;-)
> After all this Renesas hardware has a lot in common with the RX I've
> been looking at recently.
>
>>
>>>
>>> CI report:
>>> https://travis-ci.org/github/philmd/qemu/builds/692828388
>>>
>>> Regards,
>>>
>>> Phil.
>>>
>>> Philippe Mathieu-Daudé (3):
>>> hw/sh4: Use MemoryRegion typedef
>>> hw/sh4: Extract timer definitions to 'hw/timer/tmu012.h'
>>> hw/timer/sh_timer: Remove unused 'qemu/timer.h' include
>>>
>>> Thomas Huth (2):
>>> tests/acceptance: Add boot tests for sh4 QEMU advent calendar image
>>> .travis.yml: Test SH4 QEMU advent calendar image
>>>
>>> include/hw/sh4/sh.h | 12 +-----------
>>> include/hw/timer/tmu012.h | 23 +++++++++++++++++++++++
>>> hw/sh4/sh7750.c | 1 +
>>> hw/timer/sh_timer.c | 3 ++-
>>> .travis.yml | 2 +-
>>> tests/acceptance/boot_linux_console.py | 13 +++++++++++--
>>> 6 files changed, 39 insertions(+), 15 deletions(-)
>>> create mode 100644 include/hw/timer/tmu012.h
>>
>>
--
Alex Bennée
prev parent reply other threads:[~2020-06-01 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 9:23 [PATCH 0/5] hw/sh4: current patch queue Philippe Mathieu-Daudé
2020-05-30 9:23 ` [PATCH 1/5] hw/sh4: Use MemoryRegion typedef Philippe Mathieu-Daudé
2020-05-30 9:23 ` [PATCH 2/5] hw/sh4: Extract timer definitions to 'hw/timer/tmu012.h' Philippe Mathieu-Daudé
2020-05-30 9:23 ` [PATCH 3/5] hw/timer/sh_timer: Remove unused 'qemu/timer.h' include Philippe Mathieu-Daudé
2020-05-30 9:23 ` [PATCH 4/5] tests/acceptance: Add boot tests for sh4 QEMU advent calendar image Philippe Mathieu-Daudé
2020-05-30 9:23 ` [PATCH 5/5] .travis.yml: Test SH4 " Philippe Mathieu-Daudé
2020-05-31 10:18 ` Alex Bennée
2020-05-31 10:18 ` [PATCH 0/5] hw/sh4: current patch queue Alex Bennée
2020-06-01 9:11 ` Philippe Mathieu-Daudé
2020-06-01 10:32 ` Alex Bennée [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=87tuzv6pq4.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=magnus.damm@gmail.com \
--cc=philmd@redhat.com \
--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 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).