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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2024122018-groove-glitzy-f3bc@gregkh>
Date: Fri, 20 Dec 2024 13:21:51 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Kever Yang <kever.yang@...k-chips.com>
Cc: heiko@...ech.de, linux-rockchip@...ts.infradead.org,
	Simon Xue <xxm@...k-chips.com>, Lee Jones <lee@...nel.org>,
	dri-devel@...ts.freedesktop.org, Zhang Rui <rui.zhang@...el.com>,
	Elaine Zhang <zhangqing@...k-chips.com>, linux-clk@...r.kernel.org,
	Conor Dooley <conor+dt@...nel.org>, FUKAUMI Naoki <naoki@...xa.com>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Andrew Lunn <andrew+netdev@...n.ch>, Andy Yan <andyshrk@....com>,
	Michael Riesch <michael.riesch@...fvision.net>,
	Andi Shyti <andi.shyti@...nel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
	linux-pm@...r.kernel.org, Ulf Hansson <ulf.hansson@...aro.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-spi@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
	Thomas Zimmermann <tzimmermann@...e.de>,
	Jose Abreu <joabreu@...opsys.com>, Jamie Iles <jamie@...ieiles.com>,
	Detlev Casanova <detlev.casanova@...labora.com>,
	Chris Morgan <macromorgan@...mail.com>,
	Frank Wang <frank.wang@...k-chips.com>, linux-mmc@...r.kernel.org,
	Linus Walleij <linus.walleij@...aro.org>, linux-i2c@...r.kernel.org,
	Simona Vetter <simona@...ll.ch>,
	Finley Xiao <finley.xiao@...k-chips.com>,
	Krzysztof Wilczyński <kw@...ux.com>,
	linux-stm32@...md-mailman.stormreply.com,
	linux-watchdog@...r.kernel.org, David Wu <david.wu@...k-chips.com>,
	Shresth Prasad <shresthprasad7@...il.com>,
	linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Lukasz Luba <lukasz.luba@....com>,
	Jisheng Zhang <jszhang@...nel.org>,
	Guenter Roeck <linux@...ck-us.net>, linux-iio@...r.kernel.org,
	linux-pci@...r.kernel.org, David Airlie <airlied@...il.com>,
	linux-phy@...ts.infradead.org, Jonas Karlman <jonas@...boo.se>,
	Maxime Ripard <mripard@...nel.org>,
	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
	Vinod Koul <vkoul@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
	Kishon Vijay Abraham I <kishon@...nel.org>,
	Alexandre Torgue <alexandre.torgue@...s.st.com>,
	Jonathan Cameron <jic23@...nel.org>,
	Jiri Slaby <jirislaby@...nel.org>, linux-pwm@...r.kernel.org,
	Rob Herring <robh@...nel.org>,
	Wim Van Sebroeck <wim@...ux-watchdog.org>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>, Mark Brown <broonie@...nel.org>,
	Dragan Simic <dsimic@...jaro.org>,
	Sebastian Reichel <sebastian.reichel@...labora.com>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	Stephen Boyd <sboyd@...nel.org>, Johan Jonker <jbx6244@...il.com>,
	Shawn Lin <shawn.lin@...k-chips.com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	linux-serial@...r.kernel.org,
	Maxime Coquelin <mcoquelin.stm32@...il.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	devicetree@...r.kernel.org,
	Diederik de Haas <didi.debian@...ow.org>,
	Michael Turquette <mturquette@...libre.com>,
	Tim Lunn <tim@...thertop.org>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
	netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>,
	Uwe Kleine-König <ukleinek@...nel.org>
Subject: Re: [PATCH 00/38] rockchip: Add rk3562 support

On Fri, Dec 20, 2024 at 06:37:46PM +0800, Kever Yang wrote:
> 
> This patch set adds rk3562 SoC and its evb support.
> 
> The patch number is a little bit too big, some of them may need to split
> out for different maintainers, please let me know which patch need to
> split out.

I recommend you doing the split-apart as you know the dependencies here
the best, right?  Otherwise we all will just probably ignore them
assuming someone else is going to review/accept them...

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ