All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: chen huacai <zltjiangshi@gmail.com>,
	Aleksandar Markovic <amarkovic@wavecomp.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
	"hpoussin@reactos.org" <hpoussin@reactos.org>,
	Huacai Chen <chenhc@lemote.com>,
	"aleksandar.rikalo@rt-rk.com" <aleksandar.rikalo@rt-rk.com>,
	"aurelien@aurel32.net" <aurelien@aurel32.net>
Subject: Re: [EXTERNAL]Re: [PATCH v2 2/5] MAINTAINERS: Adjust maintainership for Fulong 2E board
Date: Thu, 14 Nov 2019 14:50:43 +0100	[thread overview]
Message-ID: <4a94a570-301b-e2db-6090-929e63f907cd@redhat.com> (raw)
In-Reply-To: <CABDp7VoVpZsQpDc7U4uJ1B7ZVCc8A2KO5qNaOucHQH6xUdX8tQ@mail.gmail.com>

On 11/14/19 2:08 PM, chen huacai wrote:
> Hi, all,
> 
> On Thu, Nov 14, 2019 at 8:34 PM Aleksandar Markovic
> <amarkovic@wavecomp.com> wrote:
>>
>> Hi, Philippe,
>>
>>> From: Philippe Mathieu-Daudé <philmd@redhat.com>
>>>
>>> Hi Aleksandar,
>>>
>>> On 11/13/19 2:47 PM, Aleksandar Markovic wrote:
>>>> From: Aleksandar Markovic <amarkovic@wavecomp.com>
>>>>
>>>> Change the maintainership for Fulong 2E board to improve its quality.
>>>
>>> IIRC you told me once this board is named Fuloong, and its CPU is a
>> ‎> Loongson, both with 2x 'o' :) I have a patch renaming the various
>>> occurrences.
>>>
>>
>> I still think that the oficial name is "Fuloong 2E", however, it is
>> shortened to "Fulong 2E" quite often in communication, and, it seems,
>> sometimes even in various docs/app notes etc.
>>
>> Can perhaps Huacai Chen enlighten us regarding the right spelling?
> The right spelling is Fuloong.
> 
[...]>>> The original author is active on the Linux kernel, let ask him 
if he'd
>>> be OK to keep an eye on his work.
>>>
>>> Huacai, would you agree to be listed as a reviewer on the Fuloong
>>> related QEMU files? You don't have to worry about the generic QEMU code
>>> plate (like keeping API up to date) I'll manage that, but I'd like to
>>> have you listed to assert the hardware is properly modeled.
>>>
>>> You would appear as:
>>> R: Huacai Chen <chenhc@lemote.com>
>>>
>>
>> That is a great idea!
>>
>> Please, Chen, get involved, you would be very welcomed, there is a place
>> for you in QEMU community!
> I'm sorry that I'm busy now, but I think I will do something in QEMU
> in the next year.

No problem, we'll keep in touch.

>>>> +R: Hervé Poussineau <hpoussin@reactos.org>
>>>
>>> I don't think Hervé is interested by this board, he has not modified the
>>> code.
>>>
>>>> +R: Aleksandar Markovic <amarkovic@wavecomp.com>
>>>> +S: Maintained
>>>
>>> Let keep it as "Odd Fixes" :)
>>>
>>
>> OK.
>>
>>>     Odd Fixes:   It has a maintainer but they don't have
>>>                  time to do much other than throw the odd
>>>                  patch in.
>>>
>>>>    F: hw/mips/mips_fulong2e.c
>>>>    F: hw/isa/vt82c686.c
>>>>    F: hw/pci-host/bonito.c
>>>>
>>>
>>> So the patch would be:
>>>
>>> -- 8< --
>>>    Fulong 2E
>>> -M: Aleksandar Markovic <amarkovic@wavecomp.com>
>>> -R: Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>
>>> +M: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>> +R: Aleksandar Markovic <amarkovic@wavecomp.com>
>>> +R: Huacai Chen <chenhc@lemote.com>
>>>    S: Odd Fixes
>>>    F: hw/mips/mips_fulong2e.c
>>>    F: hw/isa/vt82c686.c
>>
>> Plus possible s/Fulong 2E/Fuloong 2E/

I'd prefer to keep this change for later, with the patch cleaning its 
use in the codebase (not that trivial because we need to alias the 
machine name to keep backward compatibility).

>>
>>> ---
>>>
>>> But let's wait to see what Huacai Chen thinks of it, before posting it.

Aleksandar, can you stay as co-maintainer?

The patch would be:

-- 8< --
    Fulong 2E
+M: Philippe Mathieu-Daudé <f4bug@amsat.org>
  M: Aleksandar Markovic <amarkovic@wavecomp.com>
-R: Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>
    S: Odd Fixes
    F: hw/mips/mips_fulong2e.c
    F: hw/isa/vt82c686.c
---

Either this way, or if you prefer to be listed with a R-tag:
Acked-by: Philippe Mathieu-Daudé <f4bug@amsat.org>



  reply	other threads:[~2019-11-14 13:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 13:47 [PATCH v2 0/5] MAINTAINERS: Fine adjustment for (mostly mips) content Aleksandar Markovic
2019-11-13 13:47 ` [PATCH v2 1/5] MAINTAINERS: Add a section on UI translation Aleksandar Markovic
2019-11-13 18:52   ` Philippe Mathieu-Daudé
2019-11-13 13:47 ` [PATCH v2 2/5] MAINTAINERS: Adjust maintainership for Fulong 2E board Aleksandar Markovic
2019-11-14 11:49   ` Philippe Mathieu-Daudé
2019-11-14 12:33     ` [EXTERNAL]Re: " Aleksandar Markovic
2019-11-14 13:08       ` chen huacai
2019-11-14 13:50         ` Philippe Mathieu-Daudé [this message]
2019-11-25 22:58           ` Philippe Mathieu-Daudé
2019-11-26 11:19             ` BALATON Zoltan
2019-12-07 19:07           ` Aleksandar Markovic
2019-11-13 13:47 ` [PATCH v2 3/5] MAINTAINERS: Adjust maintainership for Malta board Aleksandar Markovic
2019-11-14 21:23   ` Philippe Mathieu-Daudé
2019-12-07 19:15     ` Aleksandar Markovic
2019-12-09  5:20       ` Markus Armbruster
2019-11-13 13:47 ` [PATCH v2 4/5] MAINTAINERS: Adjust maintainership for R4000 systems Aleksandar Markovic
2019-11-22 13:58   ` Philippe Mathieu-Daudé
2019-11-22 14:14     ` Aleksandar Markovic
2019-11-22 15:29       ` Philippe Mathieu-Daudé
2019-11-22 23:01         ` Hervé Poussineau
2019-11-13 13:47 ` [PATCH v2 5/5] MAINTAINERS: Add two files to Malta section Aleksandar Markovic
2019-11-22 20:28   ` Philippe Mathieu-Daudé
2019-11-22 20:37     ` Aleksandar Markovic
2019-11-23 13:44       ` Philippe Mathieu-Daudé
2019-11-23 14:18         ` Aleksandar Markovic

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=4a94a570-301b-e2db-6090-929e63f907cd@redhat.com \
    --to=philmd@redhat.com \
    --cc=aleksandar.markovic@rt-rk.com \
    --cc=aleksandar.rikalo@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=chenhc@lemote.com \
    --cc=hpoussin@reactos.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zltjiangshi@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 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.