From: Greg KH <gregkh@linuxfoundation.org>
To: Dileep Sankhla <dileepsankhla.ds@gmail.com>
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, pure.logic@nexus-software.ie,
johan@kernel.org, elder@kernel.org
Subject: Re: tree for the greybus subsystem
Date: Sat, 24 Feb 2024 06:27:41 +0100 [thread overview]
Message-ID: <2024022427-abruptly-vastness-ed23@gregkh> (raw)
In-Reply-To: <CAHxc4buV_UieeVVBhua3vmT2+2e6qf2B9uoxpSPAg6faGBa=Ww@mail.gmail.com>
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
next prev parent reply other threads:[~2024-02-24 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 18:14 tree for the greybus subsystem Dileep Sankhla
2024-02-24 5:27 ` Greg KH [this message]
2024-02-25 9:11 ` Dileep Sankhla
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=2024022427-abruptly-vastness-ed23@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dileepsankhla.ds@gmail.com \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=pure.logic@nexus-software.ie \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox