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: <20201113205959.42q6p4enm7lem2if@facebook>
Date:   Fri, 13 Nov 2020 14:59:59 -0600
From:   Nishanth Menon <nm@...com>
To:     Peter Ujfalusi <peter.ujfalusi@...com>,
        Roger Quadros <rogerq@...com>,
        Tony Lindgren <tony@...mide.com>,
        Tero Kristo <t-kristo@...com>, Jyri Sarha <jsarha@...com>,
        Tomi Valkeinen <tomi.valkeinen@...com>,
        Keerthy <j-keerthy@...com>, Lokesh Vutla <lokeshvutla@...com>,
        Rob Herring <robh+dt@...nel.org>
CC:     <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V3 0/5] arm64: dts: ti: Cleanup mix of "okay" and
 "disabled"

On 07:07-20201113, Nishanth Menon wrote:
> On Thu, 12 Nov 2020 12:35:33 -0600, Nishanth Menon wrote:
> > Changes since v2[3]:
> > - Rebase on top of ti-k3-dts-next (no functional changes)
> > - picked up reviewed-by and acks from folks.
> > 
> > Since we have all the required acks and reviews, I will apply this
> > series tomorrow morning since this can cause churn for other folks.
> > 
> > [...]
> 
> Hi,
> 
> I have applied the following to branch ti-k3-dts-next on [1].
> Thank you!
> 
> [1/5] arm64: dts: ti: k3-am65*: Cleanup disabled nodes at SoC dtsi level
>       commit: 957c8a49d2ed0d9ed710c8643d43912b64a3708a
> [2/5] arm64: dts: ti: k3-j721e*: Cleanup disabled nodes at SoC dtsi level
>       commit: f388cb320905e0908429ce5ce8b14b5fadb6a1ea
> [3/5] arm64: dts: ti: am65/j721e: Fix up un-necessary status set to "okay" for crypto
>       commit: 2fcb0ff200d0c9b0c5cab541cc8f8444d937e9ca
> [4/5] arm64: dts: ti: k3-am654-base-board: Fix up un-necessary status set to "okay" for USB
>       commit: 399e08d521a34ca8180c8eaeaf181176ace85b47
> [5/5] arm64: dts: ti: am65/j721e/j7200: Mark firmware used uart as "reserved"
>       commit: cf2e8c96b52984319c27f1e0b68fbef712df9bb9
> 
> 
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent up the chain during
> the next merge window (or sooner if it is a relevant bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
> 
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
> 
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
> 
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
> 


I will drop this series from my tree - Fixes: tags on the patches should
be dropped as it is not strictly to the stable tree rules and can
potentially cause conflicts when backported.

I will repost the next version dropping the same and pick the new series
up instead.

Apologies on the churn (and thanks Peter, Sekhar for the offline
feedback - better safe than sorry).

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ