From: BALATON Zoltan <balaton@eik.bme.hu>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Gerd Hoffmann <kraxel@redhat.com>,
Sebastian Bauer <mail@sebastianbauer.info>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] hw/display/sm501* status
Date: Mon, 16 Jul 2018 22:26:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.BSF.2.21.1807162207210.15021@zero.eik.bme.hu> (raw)
In-Reply-To: <20180716025346.GF2599@umbus.fritz.box>
On Mon, 16 Jul 2018, David Gibson wrote:
> On Sun, Jul 15, 2018 at 11:29:56AM +0200, BALATON Zoltan wrote:
>> So before sending more patches I'd like to clear who can review and merge
>> patches for sm501 in the future and what is the maintainership of this
>> device?
>
> The unfortunate answer is that there isn't any great choice: that's
> basically what having no maintainer means.
>
> I suspect Gerd is the most qualified to review patches to this
> technically, but even then that's only by general familiarity with
> display devices.
>
> At Peter's request, I'm willing to take sm501 patches through the ppc
> tree. Since I can't review the patches in depth, I'd be pretty much
> taking anything you send unless there's something obviously bogus.
>
> .. which would make you de facto sub-maintainer of sm501. Given
> which, I encourage you again to become *actual* maintainer; there
> really is no-one better qualified at this point. I realize that you
> don't want to make a big ongoing job of thise, but AFAIK that's
> exactly what the "Odd Fixes" maintainership status exists for.
There's already a section for sam460ex in MAINTAINERS where I've claimed
some devices that I've added and used by this machine. I did not take
sm501 because it was part of SH4 R2D but surprisingly it's not listed
there either and the maintainer listed there remained silent so far so it
seems that is not maintained any more.
I could list sm501 in the sam460ex section thus formally taking
sub-maintainership but this would only go as far that I'll get cc-d on
changes and try to review them. I still can't (and don't want to) maintain
my own tree and send pull requests directly so I'd need someone's help
with that who can take my patches and merge them via their tree. If it's
OK to continue to use the PPC tree for that I'm fine with that if David
agrees (which I think he did above).
So is it OK to add sm501 to sam460ex section so I claim responsibility for
changes and will continue sending patches cc-ing David (and maybe Gerd to
help spotting problems) then David could take these via the PPC tree?
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2018-07-16 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 9:29 [Qemu-devel] hw/display/sm501* status BALATON Zoltan
2018-07-16 2:53 ` David Gibson
2018-07-16 20:26 ` BALATON Zoltan [this message]
2018-07-16 20:43 ` Peter Maydell
2018-07-18 2:30 ` David Gibson
2018-07-18 20:06 ` Sebastian Bauer
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=alpine.BSF.2.21.1807162207210.15021@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=aurelien@aurel32.net \
--cc=david@gibson.dropbear.id.au \
--cc=kraxel@redhat.com \
--cc=magnus.damm@gmail.com \
--cc=mail@sebastianbauer.info \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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.