Hello,
I am fixing a coding style problem in the loopback bridge driver for the Greybus loopback module. The source code file (please see [0]) is located in the staging tree for the linux-next.
In order to create the patch, I need to find the right development tree. I checked the MAINTAINERS file for the Greybus subsystem development tree but could not find one. I also searched [1] for "greybus", but without success.
What is the development tree for the greybus subsystem?
Regards, Dileep
[0]: drivers/staging/greybus/loopback.c [1]: https://git.kernel.org/pub/scm/linux/kernel/git/
On Fri, Feb 23, 2024 at 11:44:48PM +0530, Dileep Sankhla wrote:
Hello,
I am fixing a coding style problem in the loopback bridge driver for the Greybus loopback module. The source code file (please see [0]) is located in the staging tree for the linux-next.
In order to create the patch, I need to find the right development tree. I checked the MAINTAINERS file for the Greybus subsystem development tree but could not find one. I also searched [1] for "greybus", but without success.
What is the development tree for the greybus subsystem?
As the staging subsystem is how this code flows into the tree:
$ ./scripts/get_maintainer.pl drivers/staging/greybus/loopback.c "Bryan O'Donoghue" pure.logic@nexus-software.ie (maintainer:GREYBUS LOOPBACK DRIVER) Johan Hovold johan@kernel.org (maintainer:GREYBUS SUBSYSTEM) Alex Elder elder@kernel.org (maintainer:GREYBUS SUBSYSTEM) Greg Kroah-Hartman gregkh@linuxfoundation.org (maintainer:GREYBUS SUBSYSTEM) greybus-dev@lists.linaro.org (moderated list:GREYBUS SUBSYSTEM) linux-staging@lists.linux.dev (open list:STAGING SUBSYSTEM) linux-kernel@vger.kernel.org (open list)
Then the staging.git tree as shown in MAINTAINERS is the correct one.
But you should always be able to just use linux-next as a default if you can't figure out what tree to use.
thanks,
greg k-h
On Sat, Feb 24, 2024 at 10:57 AM Greg KH gregkh@linuxfoundation.org wrote:
Then the staging.git tree as shown in MAINTAINERS is the correct one.
Hello Greg,
Thank you for your reply.
I have submitted my patch against the staging.git tree, branch staging-next.
Regards, Dileep