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: <DB6PR0402MB275830516E1930F051982B88E0999@DB6PR0402MB2758.eurprd04.prod.outlook.com>
Date:   Tue, 2 Mar 2021 05:19:56 +0000
From:   Kuldeep Singh <kuldeep.singh@....com>
To:     Mark Brown <broonie@...nel.org>
CC:     "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Ashish Kumar <ashish.kumar@....com>, Han Xu <han.xu@....com>
Subject: RE: [EXT] Re: [PATCH 2/3] spi: spi-nxp-fspi: Add driver support for
 imx8dxl

> > I have converted bindings to yaml version in the patch and also added
> imx8dxl compatible along-with the conversion. Please see the difference in
> compatible entries from txt to yaml conversion[1].
> > Kindly let me know do I need to submit different patch for adding new
> compatible or ok to include in the conversion patch itself?
> 
> Your YAML binding conversion should have been a standalone patch only
> doing that conversion, the new compatible should have been split out and
> gone first - each patch should only do one thing as covered in submitting-
> patches.rst.  As things stand the changelog for the conversion is misleading
> since it doesn't mention the new compatible.

Thanks Mark for mentioning.
I will send compatible adding patch with this series and post yaml conversion later.

Regards
Kuldeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ