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] [day] [month] [year] [list]
Message-ID: <61607306.matp6XCIr4@diego>
Date: Thu, 29 Aug 2024 13:52:37 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Detlev Casanova <detlev.casanova@...labora.com>,
 Guenter Roeck <linux@...ck-us.net>
Cc: linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
 Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
 David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
 Andi Shyti <andi.shyti@...nel.org>, Jonathan Cameron <jic23@...nel.org>,
 Lars-Peter Clausen <lars@...afoo.de>, Lee Jones <lee@...nel.org>,
 Ulf Hansson <ulf.hansson@...aro.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Jiri Slaby <jirislaby@...nel.org>, Mark Brown <broonie@...nel.org>,
 Wim Van Sebroeck <wim@...ux-watchdog.org>,
 Chris Morgan <macromorgan@...mail.com>, Jonas Karlman <jonas@...boo.se>,
 Tim Lunn <tim@...thertop.org>, Chukun Pan <amadeus@....edu.cn>,
 Andy Yan <andyshrk@....com>, Muhammed Efe Cetin <efectn@...tonmail.com>,
 Jagan Teki <jagan@...eble.ai>, Dragan Simic <dsimic@...jaro.org>,
 Ondrej Jirman <megi@....cz>, Michael Riesch <michael.riesch@...fvision.net>,
 Jimmy Hon <honyuenkwun@...il.com>, Alexey Charkov <alchark@...il.com>,
 Elon Zhang <zhangzj@...k-chips.com>, Elaine Zhang <zhangqing@...k-chips.com>,
 Yifeng Zhao <yifeng.zhao@...k-chips.com>,
 Finley Xiao <finley.xiao@...k-chips.com>, Liang Chen <cl@...k-chips.com>,
 Jisheng Zhang <jszhang@...nel.org>, Jamie Iles <jamie@...ieiles.com>,
 devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-rockchip@...ts.infradead.org, dri-devel@...ts.freedesktop.org,
 linux-i2c@...r.kernel.org, linux-iio@...r.kernel.org,
 linux-mmc@...r.kernel.org, linux-serial@...r.kernel.org,
 linux-spi@...r.kernel.org, linux-watchdog@...r.kernel.org,
 kernel@...labora.com
Subject:
 Re: [PATCH v2 09/12] dt-bindings: watchdog: Add rockchip,rk3576-wdt
 compatible

Hi Guenter,

Am Dienstag, 27. August 2024, 21:38:35 CEST schrieb Guenter Roeck:
> On 8/27/24 00:20, Heiko Stübner wrote:
> > Am Samstag, 24. August 2024, 18:44:29 CEST schrieb Guenter Roeck:
> >> On Fri, Aug 23, 2024 at 10:52:36AM -0400, Detlev Casanova wrote:
> >>> It is compatible with the other rockchip SoCs.
> >>>
> >>> Signed-off-by: Detlev Casanova <detlev.casanova@...labora.com>
> >>
> >> Acked-by: Guenter Roeck <linux@...ck-us.net>
> > 
> > For my understanding, does this Ack mean you expect the patch to go in
> > with the other patches?
> > 
> Yes
> 
> > Because in theory this patch could also be picked and go through the
> > watchdog tree, similar to how the saradc binding went into the
> > iio tree already.
> > 
> 
> I thought it was all supposed to be pushed together.

I think at this point the rk3576 has still quite a number of separate
pieces. A series for clocks, one for mmc and I think there are more.

So for stuff that is obvious, like the saradc compatible Jonathan already,
picked or this watchdog compatible, a strategy of "someone picks the
individual" patch also is helpful, because it reduces the number of pieces
on the "chess board" ;-) .


So I guess both ways (wdt binding getting applied, or me just applying it
with the rest) are doable and we'll just follow what you feel comfortable
with doing.

Heiko





Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ