MAINTAINERS: Renesas #55167
MAINTAINERS: Renesas #55167
Conversation
7c0774a
to
97aabee
Compare
|
Btw. it seems that @pmarzin has not been added to the collaborator list, is he still collaborating on the R-Car platform? |
|
@str4t0m what is you relation to Renesas and this platform? The platform was originally submitted by someone else. @andrzej-kaczmarek |
|
@nashif I don't don't have any relation to Renesas. Checking new PRs I just noticed that all new smartbond PRs from @blauret were assigned to Renesas R-Car, therefore I had a look why this is happening and attempted to fix it. |
|
@str4t0m appreciate that you want to step in, but in this case we need to wait for the original contributors. |
|
sorry, long day, for misread the change and thought you are claiming maintainership for this, which is not the case :) |
There was a problem hiding this comment.
Hi @str4t0m, sorry for the delay, I was on holidays.
Thank you for your suggestion, I had planned to correct this problem soon so that's fine.
@pmarzin is indeed still a collaborator on the "renesas r-car" part.
The only suggestion I would have is to name the new area and label "Renesas Smartbond" as you are precisely delimiting target files to this soc family.
I saw that you wanted to delimit this area to "not r-car socs" but because of how file tree is done right now, you can't really do that.
After the introduction of the renesas smartbond family the scope of dts files needs to be limited to the rcar subfolder. Signed-off-by: Thomas Stranger <[email protected]>
Renesas SmartBond platform only had an entry for the maintainer of the hal. Signed-off-by: Thomas Stranger <[email protected]>
ce3a6b8
97aabee
to
ce3a6b8
Compare
I noticed that all new PRs for the Smartbond SoCs were wrongly assigned to the R-Car platform therefore I am proposing the following commits.
files needs to be limited to the R-Car subfolder.
As @andrzej-kaczmarek is the maintainer of the HAL I assume that he is also maintaining the zephyr side, please let me know if this is no longer the case.
See also HAL module request, introduction of platform, and PR Renesas HAL maintainer