I am a top reviewer mainly for MediaTek SoC related patches in most
subsystems and I've also been upstreaming both improvements, fixes
and new drivers and devicetrees when required.
The MediaTek scene saw a generous increase in number of patches that
are sent to the lists every week, increasing the amount of required
efforts to maintain the MTK bits overall, and we will possibly see
even more of that.
For this reason, and also because of suggestions and encouragement
coming from the community, I'm stepping up to be a co-maintainer of
MediaTek SoCs support.
Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
---
P.S.: I tried to reach to Matthias for almost two months, but I couldn't
find any way to talk to him and he has been unresponsive on the mailing
lists as well.
P.P.S.: This also comes after Rob Herring's suggestion to have myself as
a MediaTek SoC co-maintainer [1] and support from other people.
[1]: https://lore.kernel.org/all/[email protected]/
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 208cfcc1aee3..211a8322c801 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2330,7 +2330,7 @@ F: drivers/rtc/rtc-mt7622.c
ARM/Mediatek SoC support
M: Matthias Brugger <[email protected]>
-R: AngeloGioacchino Del Regno <[email protected]>
+M: AngeloGioacchino Del Regno <[email protected]>
L: [email protected]
L: [email protected] (moderated for non-subscribers)
L: [email protected] (moderated for non-subscribers)
--
2.42.0
On Fri, Sep 29, 2023, at 04:20, AngeloGioacchino Del Regno wrote:
> I am a top reviewer mainly for MediaTek SoC related patches in most
> subsystems and I've also been upstreaming both improvements, fixes
> and new drivers and devicetrees when required.
>
> The MediaTek scene saw a generous increase in number of patches that
> are sent to the lists every week, increasing the amount of required
> efforts to maintain the MTK bits overall, and we will possibly see
> even more of that.
>
> For this reason, and also because of suggestions and encouragement
> coming from the community, I'm stepping up to be a co-maintainer of
> MediaTek SoCs support.
>
> Signed-off-by: AngeloGioacchino Del Regno
> <[email protected]>
> ---
>
> P.S.: I tried to reach to Matthias for almost two months, but I couldn't
> find any way to talk to him and he has been unresponsive on the mailing
> lists as well.
>
> P.P.S.: This also comes after Rob Herring's suggestion to have myself as
> a MediaTek SoC co-maintainer [1] and support from other people.
>
> [1]: https://lore.kernel.org/all/[email protected]/
Thanks for volunteering for this!
I have no information on what Mattias is doing, but I see that he
has not merged any patches since June, and that he never sent a
pull request for your patches that are still in his for-next
branch.
I hope he's going to be ok, but let's plan for you to take over
for the moment, at least until Matthias is again able to keep
maintaining the platform in the near future.
Here is my suggestion for how to continue from here:
- Please send your MAINTAINERS file update to [email protected]
along with any urgent bugfixes you may have, so I can forward
them for 6.7. I'm wrapping up the current set of fixes at
the moment, so this would be for next week's rc
- Create a git tree with the ususal branches (drivers, soc, dt,
fixes, for-next) and ask Stephen Rothwell (on Cc) to add
the combined for-next branch to linux-next for integration testing
- Start each branch on 6.6-rc2 (usually we use rc1, but this time
rc2 is a better candidate because of the last-minute
drivers/pmdomain rename), and merge the corresponding branches
from git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git
into those to avoids conflicts with his tree
- Add any further patches you want in 6.7 on top
- Send a first set of pull requests to [email protected] for whatever
you have merged as soon as you are confident about them,
ideally by the end of next week.
- Send additional pull requests for fixups or late features in
the weeks after that as you see fit.
See Documentation/process/maintainer-soc.rst for more details
on the above. When Mattias comes back, you can work out a new
process together with him.
Arnd
Am 29. September 2023 10:20:09 MESZ schrieb AngeloGioacchino Del Regno <[email protected]>:
>I am a top reviewer mainly for MediaTek SoC related patches in most
>subsystems and I've also been upstreaming both improvements, fixes
>and new drivers and devicetrees when required.
>
>The MediaTek scene saw a generous increase in number of patches that
>are sent to the lists every week, increasing the amount of required
>efforts to maintain the MTK bits overall, and we will possibly see
>even more of that.
>
>For this reason, and also because of suggestions and encouragement
>coming from the community, I'm stepping up to be a co-maintainer of
>MediaTek SoCs support.
>
>Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
>---
>
>P.S.: I tried to reach to Matthias for almost two months, but I couldn't
>find any way to talk to him and he has been unresponsive on the mailing
>lists as well.
>
>P.P.S.: This also comes after Rob Herring's suggestion to have myself as
>a MediaTek SoC co-maintainer [1] and support from other people.
>
>[1]: https://lore.kernel.org/all/[email protected]/
>
Hi,
Thank you Angelo for supporting Matthias here. I also have no information why his tree is stale for more than 2 months and also got no response on direct contact. I hope he is still ok and do only need some free time.
I waiting for these to be merged:
https://patchwork.kernel.org/project/linux-mediatek/list/?series=761293 https://patchwork.kernel.org/project/linux-mediatek/list/?series=777712
Do you have created an own tree from matthias' one or can you directly work on it? If working on own tree please send me the link,so that i can track when changes (also from others) are merged.
regards Frank
On Mon, Oct 2, 2023 at 4:27 PM AngeloGioacchino Del Regno
<[email protected]> wrote:
>
> Il 02/10/23 05:30, Chen-Yu Tsai ha scritto:
> > On Sat, Sep 30, 2023 at 3:37 AM Arnd Bergmann <[email protected]> wrote:
> >>
> >> On Fri, Sep 29, 2023, at 04:20, AngeloGioacchino Del Regno wrote:
> >>> I am a top reviewer mainly for MediaTek SoC related patches in most
> >>> subsystems and I've also been upstreaming both improvements, fixes
> >>> and new drivers and devicetrees when required.
> >>>
> >>> The MediaTek scene saw a generous increase in number of patches that
> >>> are sent to the lists every week, increasing the amount of required
> >>> efforts to maintain the MTK bits overall, and we will possibly see
> >>> even more of that.
> >>>
> >>> For this reason, and also because of suggestions and encouragement
> >>> coming from the community, I'm stepping up to be a co-maintainer of
> >>> MediaTek SoCs support.
> >>>
> >>> Signed-off-by: AngeloGioacchino Del Regno
> >>> <[email protected]>
> >>> ---
> >>>
> >>> P.S.: I tried to reach to Matthias for almost two months, but I couldn't
> >>> find any way to talk to him and he has been unresponsive on the mailing
> >>> lists as well.
> >>>
> >>> P.P.S.: This also comes after Rob Herring's suggestion to have myself as
> >>> a MediaTek SoC co-maintainer [1] and support from other people.
> >>>
> >>> [1]: https://lore.kernel.org/all/[email protected]/
> >>
> >> Thanks for volunteering for this!
> >>
> >> I have no information on what Mattias is doing, but I see that he
> >> has not merged any patches since June, and that he never sent a
> >> pull request for your patches that are still in his for-next
> >> branch.
> >>
> >> I hope he's going to be ok, but let's plan for you to take over
> >> for the moment, at least until Matthias is again able to keep
> >> maintaining the platform in the near future.
> >>
> >> Here is my suggestion for how to continue from here:
> >>
> >> - Please send your MAINTAINERS file update to [email protected]
> >> along with any urgent bugfixes you may have, so I can forward
> >> them for 6.7. I'm wrapping up the current set of fixes at
> >> the moment, so this would be for next week's rc
> >>
> >> - Create a git tree with the ususal branches (drivers, soc, dt,
> >> fixes, for-next) and ask Stephen Rothwell (on Cc) to add
> >> the combined for-next branch to linux-next for integration testing
> >
> > I suggest creating a shared git tree from the start. That way when
> > Mattias comes back and does agree to co-maintainership, or if anyone
> > else joins in, you don't have to change the git tree URL in a lot of
> > places.
> >
>
> I agree with creating a shared git tree from the start... I currently don't have
> a kernel.org account yet, as I'm waiting for helpdesk to grant my account request.
>
> They asked me to send a patch adding myself to MAINTAINERS as they would use that
> as a basis to grant the account request... so I guess it's happening soon; seen
> the urgency, I would do anything in my power to speed up the process, but probably
> there's "nothing to do" about it.
If you do end up not getting an account in time, I can do all the patch
queuing and sending out PR work using my account for this cycle, if that's
OK with the soc maintainers.
That said, we have a long weekend (Oct. 7 to Oct. 10) during which I will be
travelling. I might also be travelling during parts of the remaining three
work days, but the whole thing is still up in the air.
> I am guessing that the right thing to do right now is to just send the mostly
> critical fixes to [email protected], along with this patch, and wait until a shared
> tree is created to keep things clean?
+1 Sounds good to me.
> >> - Start each branch on 6.6-rc2 (usually we use rc1, but this time
> >> rc2 is a better candidate because of the last-minute
> >> drivers/pmdomain rename), and merge the corresponding branches
> >> from git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git
> >> into those to avoids conflicts with his tree
> >>
> >> - Add any further patches you want in 6.7 on top
> >>
> >> - Send a first set of pull requests to [email protected] for whatever
> >> you have merged as soon as you are confident about them,
> >> ideally by the end of next week.
> >>
> >> - Send additional pull requests for fixups or late features in
> >> the weeks after that as you see fit.
> >>
> >> See Documentation/process/maintainer-soc.rst for more details
> >> on the above. When Mattias comes back, you can work out a new
> >> process together with him.
> >
> > I can also answer any questions you might have about the process.
> >
>
> Many thanks for your support, I greatly appreciate that.
>
> Cheers,
> Angelo
>
On Sat, Sep 30, 2023 at 3:37 AM Arnd Bergmann <[email protected]> wrote:
>
> On Fri, Sep 29, 2023, at 04:20, AngeloGioacchino Del Regno wrote:
> > I am a top reviewer mainly for MediaTek SoC related patches in most
> > subsystems and I've also been upstreaming both improvements, fixes
> > and new drivers and devicetrees when required.
> >
> > The MediaTek scene saw a generous increase in number of patches that
> > are sent to the lists every week, increasing the amount of required
> > efforts to maintain the MTK bits overall, and we will possibly see
> > even more of that.
> >
> > For this reason, and also because of suggestions and encouragement
> > coming from the community, I'm stepping up to be a co-maintainer of
> > MediaTek SoCs support.
> >
> > Signed-off-by: AngeloGioacchino Del Regno
> > <[email protected]>
> > ---
> >
> > P.S.: I tried to reach to Matthias for almost two months, but I couldn't
> > find any way to talk to him and he has been unresponsive on the mailing
> > lists as well.
> >
> > P.P.S.: This also comes after Rob Herring's suggestion to have myself as
> > a MediaTek SoC co-maintainer [1] and support from other people.
> >
> > [1]: https://lore.kernel.org/all/[email protected]/
>
> Thanks for volunteering for this!
>
> I have no information on what Mattias is doing, but I see that he
> has not merged any patches since June, and that he never sent a
> pull request for your patches that are still in his for-next
> branch.
>
> I hope he's going to be ok, but let's plan for you to take over
> for the moment, at least until Matthias is again able to keep
> maintaining the platform in the near future.
>
> Here is my suggestion for how to continue from here:
>
> - Please send your MAINTAINERS file update to [email protected]
> along with any urgent bugfixes you may have, so I can forward
> them for 6.7. I'm wrapping up the current set of fixes at
> the moment, so this would be for next week's rc
>
> - Create a git tree with the ususal branches (drivers, soc, dt,
> fixes, for-next) and ask Stephen Rothwell (on Cc) to add
> the combined for-next branch to linux-next for integration testing
I suggest creating a shared git tree from the start. That way when
Mattias comes back and does agree to co-maintainership, or if anyone
else joins in, you don't have to change the git tree URL in a lot of
places.
> - Start each branch on 6.6-rc2 (usually we use rc1, but this time
> rc2 is a better candidate because of the last-minute
> drivers/pmdomain rename), and merge the corresponding branches
> from git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git
> into those to avoids conflicts with his tree
>
> - Add any further patches you want in 6.7 on top
>
> - Send a first set of pull requests to [email protected] for whatever
> you have merged as soon as you are confident about them,
> ideally by the end of next week.
>
> - Send additional pull requests for fixups or late features in
> the weeks after that as you see fit.
>
> See Documentation/process/maintainer-soc.rst for more details
> on the above. When Mattias comes back, you can work out a new
> process together with him.
I can also answer any questions you might have about the process.
ChenYu
On 29/09/2023 10:20, AngeloGioacchino Del Regno wrote:
> I am a top reviewer mainly for MediaTek SoC related patches in most
> subsystems and I've also been upstreaming both improvements, fixes
> and new drivers and devicetrees when required.
>
> The MediaTek scene saw a generous increase in number of patches that
> are sent to the lists every week, increasing the amount of required
> efforts to maintain the MTK bits overall, and we will possibly see
> even more of that.
>
> For this reason, and also because of suggestions and encouragement
> coming from the community, I'm stepping up to be a co-maintainer of
> MediaTek SoCs support.
>
> Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
Thanks Angelo to volunteer on this. It actually was on my list for the last days
to ask you to help me out as I'm not able at the moment to cope with the review
process. That's unfortunate and we missed one merge window (August) where I took
no patches but after holiday situation didn't get better. I don't want to be
break in the MediaTek upstream development, so it's great to see you stepping up.
As I read in the thread, I agree the best will be to have a share tree at
kernel.org. It seems I can't share my tree with you, so hopefully you will get
access fast.
My idea is to not disappear and create a collaborative process for us on the
maintainership in the future.
> ---
>
> P.S.: I tried to reach to Matthias for almost two months, but I couldn't
> find any way to talk to him and he has been unresponsive on the mailing
> lists as well.
I think you didn't tried [email protected], but that should be no excuse
from my side for being unresponsive. Thanks for your help!
Please contact me on IRC for any coordination.
Regards,
Matthias
>
> P.P.S.: This also comes after Rob Herring's suggestion to have myself as
> a MediaTek SoC co-maintainer [1] and support from other people.
>
> [1]: https://lore.kernel.org/all/[email protected]/
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 208cfcc1aee3..211a8322c801 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2330,7 +2330,7 @@ F: drivers/rtc/rtc-mt7622.c
>
> ARM/Mediatek SoC support
> M: Matthias Brugger <[email protected]>
> -R: AngeloGioacchino Del Regno <[email protected]>
> +M: AngeloGioacchino Del Regno <[email protected]>
> L: [email protected]
> L: [email protected] (moderated for non-subscribers)
> L: [email protected] (moderated for non-subscribers)
On Sat, Sep 30, 2023 at 3:55 PM Frank Wunderlich
<[email protected]> wrote:
>
> Am 29. September 2023 10:20:09 MESZ schrieb AngeloGioacchino Del Regno <[email protected]>:
> >I am a top reviewer mainly for MediaTek SoC related patches in most
> >subsystems and I've also been upstreaming both improvements, fixes
> >and new drivers and devicetrees when required.
> >
> >The MediaTek scene saw a generous increase in number of patches that
> >are sent to the lists every week, increasing the amount of required
> >efforts to maintain the MTK bits overall, and we will possibly see
> >even more of that.
> >
> >For this reason, and also because of suggestions and encouragement
> >coming from the community, I'm stepping up to be a co-maintainer of
> >MediaTek SoCs support.
> >
> >Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
> >---
> >
> >P.S.: I tried to reach to Matthias for almost two months, but I couldn't
> >find any way to talk to him and he has been unresponsive on the mailing
> >lists as well.
> >
> >P.P.S.: This also comes after Rob Herring's suggestion to have myself as
> >a MediaTek SoC co-maintainer [1] and support from other people.
> >
> >[1]: https://lore.kernel.org/all/[email protected]/
> >
>
> Hi,
>
> Thank you Angelo for supporting Matthias here. I also have no information why his tree is stale for more than 2 months and also got no response on direct contact. I hope he is still ok and do only need some free time.
>
> I waiting for these to be merged:
> https://patchwork.kernel.org/project/linux-mediatek/list/?series=761293 https://patchwork.kernel.org/project/linux-mediatek/list/?series=777712
>
> Do you have created an own tree from matthias' one or can you directly work on it? If working on own tree please send me the link,so that i can track when changes (also from others) are merged.
It's likely going to be under a new namespace. Matthias used his own
namespace, which is not shared.
AFAIK the kernel.org git infrastructure doesn't allow others to push
to a user's namespace.
> regards Frank
>
On 29/09/2023 10:20, AngeloGioacchino Del Regno wrote:
> I am a top reviewer mainly for MediaTek SoC related patches in most
> subsystems and I've also been upstreaming both improvements, fixes
> and new drivers and devicetrees when required.
>
> The MediaTek scene saw a generous increase in number of patches that
> are sent to the lists every week, increasing the amount of required
> efforts to maintain the MTK bits overall, and we will possibly see
> even more of that.
>
> For this reason, and also because of suggestions and encouragement
> coming from the community, I'm stepping up to be a co-maintainer of
> MediaTek SoCs support.
>
> Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
Forgot that in my previous mail. Obviously:
Acked-by: Matthias Brugger <[email protected]>
> ---
>
> P.S.: I tried to reach to Matthias for almost two months, but I couldn't
> find any way to talk to him and he has been unresponsive on the mailing
> lists as well.
>
> P.P.S.: This also comes after Rob Herring's suggestion to have myself as
> a MediaTek SoC co-maintainer [1] and support from other people.
>
> [1]: https://lore.kernel.org/all/[email protected]/
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 208cfcc1aee3..211a8322c801 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2330,7 +2330,7 @@ F: drivers/rtc/rtc-mt7622.c
>
> ARM/Mediatek SoC support
> M: Matthias Brugger <[email protected]>
> -R: AngeloGioacchino Del Regno <[email protected]>
> +M: AngeloGioacchino Del Regno <[email protected]>
> L: [email protected]
> L: [email protected] (moderated for non-subscribers)
> L: [email protected] (moderated for non-subscribers)
Il 02/10/23 11:41, Matthias Brugger ha scritto:
>
>
> On 29/09/2023 10:20, AngeloGioacchino Del Regno wrote:
>> I am a top reviewer mainly for MediaTek SoC related patches in most
>> subsystems and I've also been upstreaming both improvements, fixes
>> and new drivers and devicetrees when required.
>>
>> The MediaTek scene saw a generous increase in number of patches that
>> are sent to the lists every week, increasing the amount of required
>> efforts to maintain the MTK bits overall, and we will possibly see
>> even more of that.
>>
>> For this reason, and also because of suggestions and encouragement
>> coming from the community, I'm stepping up to be a co-maintainer of
>> MediaTek SoCs support.
>>
>> Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
>
> Thanks Angelo to volunteer on this. It actually was on my list for the last days to
> ask you to help me out as I'm not able at the moment to cope with the review
> process. That's unfortunate and we missed one merge window (August) where I took no
> patches but after holiday situation didn't get better. I don't want to be break in
> the MediaTek upstream development, so it's great to see you stepping up.
>
> As I read in the thread, I agree the best will be to have a share tree at
> kernel.org. It seems I can't share my tree with you, so hopefully you will get
> access fast.
>
> My idea is to not disappear and create a collaborative process for us on the
> maintainership in the future.
>
I am really happy first of all see that you're fine, and then to see that you
are happy with me going for this.
I will be even happier to create a collaborative process for our maintainership
of MediaTek, as I was really hoping for that to happen.
>> ---
>>
>> P.S.: I tried to reach to Matthias for almost two months, but I couldn't
>> find any way to talk to him and he has been unresponsive on the mailing
>> lists as well.
>
> I think you didn't tried [email protected], but that should be no excuse from
> my side for being unresponsive. Thanks for your help!
>
> Please contact me on IRC for any coordination.
Coming to IRC for a nice chat ASAP!
Thank *you* for this email, and preventively thanks for *your* help!
Cheers,
Angelo
>
> Regards,
> Matthias
>
>
>>
>> P.P.S.: This also comes after Rob Herring's suggestion to have myself as
>> a MediaTek SoC co-maintainer [1] and support from other people.
>>
>> [1]: https://lore.kernel.org/all/[email protected]/
>>
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 208cfcc1aee3..211a8322c801 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -2330,7 +2330,7 @@ F: drivers/rtc/rtc-mt7622.c
>> ARM/Mediatek SoC support
>> M: Matthias Brugger <[email protected]>
>> -R: AngeloGioacchino Del Regno <[email protected]>
>> +M: AngeloGioacchino Del Regno <[email protected]>
>> L: [email protected]
>> L: [email protected] (moderated for non-subscribers)
>> L: [email protected] (moderated for non-subscribers)
Il 02/10/23 05:30, Chen-Yu Tsai ha scritto:
> On Sat, Sep 30, 2023 at 3:37 AM Arnd Bergmann <[email protected]> wrote:
>>
>> On Fri, Sep 29, 2023, at 04:20, AngeloGioacchino Del Regno wrote:
>>> I am a top reviewer mainly for MediaTek SoC related patches in most
>>> subsystems and I've also been upstreaming both improvements, fixes
>>> and new drivers and devicetrees when required.
>>>
>>> The MediaTek scene saw a generous increase in number of patches that
>>> are sent to the lists every week, increasing the amount of required
>>> efforts to maintain the MTK bits overall, and we will possibly see
>>> even more of that.
>>>
>>> For this reason, and also because of suggestions and encouragement
>>> coming from the community, I'm stepping up to be a co-maintainer of
>>> MediaTek SoCs support.
>>>
>>> Signed-off-by: AngeloGioacchino Del Regno
>>> <[email protected]>
>>> ---
>>>
>>> P.S.: I tried to reach to Matthias for almost two months, but I couldn't
>>> find any way to talk to him and he has been unresponsive on the mailing
>>> lists as well.
>>>
>>> P.P.S.: This also comes after Rob Herring's suggestion to have myself as
>>> a MediaTek SoC co-maintainer [1] and support from other people.
>>>
>>> [1]: https://lore.kernel.org/all/[email protected]/
>>
>> Thanks for volunteering for this!
>>
>> I have no information on what Mattias is doing, but I see that he
>> has not merged any patches since June, and that he never sent a
>> pull request for your patches that are still in his for-next
>> branch.
>>
>> I hope he's going to be ok, but let's plan for you to take over
>> for the moment, at least until Matthias is again able to keep
>> maintaining the platform in the near future.
>>
>> Here is my suggestion for how to continue from here:
>>
>> - Please send your MAINTAINERS file update to [email protected]
>> along with any urgent bugfixes you may have, so I can forward
>> them for 6.7. I'm wrapping up the current set of fixes at
>> the moment, so this would be for next week's rc
>>
>> - Create a git tree with the ususal branches (drivers, soc, dt,
>> fixes, for-next) and ask Stephen Rothwell (on Cc) to add
>> the combined for-next branch to linux-next for integration testing
>
> I suggest creating a shared git tree from the start. That way when
> Mattias comes back and does agree to co-maintainership, or if anyone
> else joins in, you don't have to change the git tree URL in a lot of
> places.
>
I agree with creating a shared git tree from the start... I currently don't have
a kernel.org account yet, as I'm waiting for helpdesk to grant my account request.
They asked me to send a patch adding myself to MAINTAINERS as they would use that
as a basis to grant the account request... so I guess it's happening soon; seen
the urgency, I would do anything in my power to speed up the process, but probably
there's "nothing to do" about it.
I am guessing that the right thing to do right now is to just send the mostly
critical fixes to [email protected], along with this patch, and wait until a shared
tree is created to keep things clean?
>> - Start each branch on 6.6-rc2 (usually we use rc1, but this time
>> rc2 is a better candidate because of the last-minute
>> drivers/pmdomain rename), and merge the corresponding branches
>> from git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git
>> into those to avoids conflicts with his tree
>>
>> - Add any further patches you want in 6.7 on top
>>
>> - Send a first set of pull requests to [email protected] for whatever
>> you have merged as soon as you are confident about them,
>> ideally by the end of next week.
>>
>> - Send additional pull requests for fixups or late features in
>> the weeks after that as you see fit.
>>
>> See Documentation/process/maintainer-soc.rst for more details
>> on the above. When Mattias comes back, you can work out a new
>> process together with him.
>
> I can also answer any questions you might have about the process.
>
Many thanks for your support, I greatly appreciate that.
Cheers,
Angelo
Hi,
Happy to see you back and fine Matthias !
Also, I'm happy to see the Angelo's step-up welcomed by everybody,
it's a great news !!!
Feel free to ask me if you need help.
Alex
AngeloGioacchino Del Regno
<[email protected]> writes:
> I am a top reviewer mainly for MediaTek SoC related patches in most
> subsystems and I've also been upstreaming both improvements, fixes
> and new drivers and devicetrees when required.
>
> The MediaTek scene saw a generous increase in number of patches that
> are sent to the lists every week, increasing the amount of required
> efforts to maintain the MTK bits overall, and we will possibly see
> even more of that.
>
> For this reason, and also because of suggestions and encouragement
> coming from the community, I'm stepping up to be a co-maintainer of
> MediaTek SoCs support.
>
> Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
Acked-by: Kevin Hilman <[email protected]>
Thank you Matthias for all the work you've put in over the years to
maintain MTK SoCs, and thank you to Angelo for stepping up to help as
the volume of maintainer work is increasing.
Kevin