All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Sebastian Bauer <mail@sebastianbauer.info>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] hw/display/sm501* status
Date: Mon, 16 Jul 2018 21:43:05 +0100	[thread overview]
Message-ID: <CAFEAcA_3km1OB=7kqoZ6AvW0+G9FqfgD+go_KghFLDrgj2Xk+g@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1807162207210.15021@zero.eik.bme.hu>

On 16 July 2018 at 21:26, BALATON Zoltan <balaton@eik.bme.hu> wrote:
> 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?

I think that makes sense. sh4 is pretty dead and if sm501's major
active user is the sam460ex then listing it there seems reasonable.

thanks
-- PMM

  reply	other threads:[~2018-07-16 20:43 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
2018-07-16 20:43     ` Peter Maydell [this message]
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='CAFEAcA_3km1OB=7kqoZ6AvW0+G9FqfgD+go_KghFLDrgj2Xk+g@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=balaton@eik.bme.hu \
    --cc=david@gibson.dropbear.id.au \
    --cc=kraxel@redhat.com \
    --cc=magnus.damm@gmail.com \
    --cc=mail@sebastianbauer.info \
    --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.