linux-kernel - Re: i2c: img-scb: remove duplicate dev

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]

Message-ID: <73cc5a7c-787c-b263-7679-0f1fa58a70f8@web.de>
Date:   Thu, 16 Apr 2020 11:46:45 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Dejin Zheng <zhengdejin5@...il.com>, linux-i2c@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, Allison Randal <allison@...utok.net>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Patrice Chotard <patrice.chotard@...com>,
        Shah Nehal-Bakulchandra <Nehal-bakulchandra.Shah@....com>,
        Tang Bin <tangbin@...s.chinamobile.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Wolfram Sang <wsa@...-dreams.de>,
        Thor Thayer <thor.thayer@...ux.intel.com>,
        Robert Richter <rrichter@...vell.com>,
        Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Barry Song <baohua@...nel.org>, kernel-janitors@...r.kernel.org
Subject: Re: i2c: img-scb: remove duplicate dev_err()

>>> Would you like to take another look at corresponding change possibilities?
>>>
>> yes, I want to do it and thanks for your info.

How do you think about to improve the clarification around potentially
“odd fixes” (because of collateral evolution)?

I noticed your update suggestion “i2c: busses: convert to devm_platform_ioremap_resource”.
https://lore.kernel.org/linux-i2c/20200409135224.7426-1-zhengdejin5@gmail.com/
https://lore.kernel.org/patchwork/patch/1222122/
https://lkml.org/lkml/2020/4/9/431

It seems that you got encouraged to contribute changes according to another
transformation approach by a single patch for a directory hierarchy.
How likely is it that such adjustments touch source code places
where related error messages would be found for further software
development considerations?
Would you like to wait until the integration of this update succeeded?

Will it be interesting in the meantime to become more familiar with
applications around scripts for the semantic patch language?
Can the Coccinelle software make the discussed transformations more convenient
also for your needs?

Regards,
Markus