lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 24 Feb 2024 06:27:41 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Dileep Sankhla <dileepsankhla.ds@...il.com>
Cc: greybus-dev@...ts.linaro.org, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org, pure.logic@...us-software.ie,
	johan@...nel.org, elder@...nel.org
Subject: Re: tree for the greybus subsystem

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@...us-software.ie> (maintainer:GREYBUS LOOPBACK DRIVER)
	Johan Hovold <johan@...nel.org> (maintainer:GREYBUS SUBSYSTEM)
	Alex Elder <elder@...nel.org> (maintainer:GREYBUS SUBSYSTEM)
	Greg Kroah-Hartman <gregkh@...uxfoundation.org> (maintainer:GREYBUS SUBSYSTEM)
	greybus-dev@...ts.linaro.org (moderated list:GREYBUS SUBSYSTEM)
	linux-staging@...ts.linux.dev (open list:STAGING SUBSYSTEM)
	linux-kernel@...r.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ