linux-kernel - R: [PATCH 2/4] drivers: pci: dwc: pci-imx6: update binding to generic name

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: <003401d60f35$3725b630$a5712290$@gmail.com>
Date:   Fri, 10 Apr 2020 14:40:26 +0200
From:   <ansuelsmth@...il.com>
To:     "'Fabio Estevam'" <festevam@...il.com>
Cc:     "'open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS'" 
        <devicetree@...r.kernel.org>,
        "'Richard Zhu'" <hongxing.zhu@....com>,
        "'Lucas Stach'" <l.stach@...gutronix.de>,
        "'Bjorn Helgaas'" <bhelgaas@...gle.com>,
        "'Rob Herring'" <robh+dt@...nel.org>,
        "'Mark Rutland'" <mark.rutland@....com>,
        "'Shawn Guo'" <shawnguo@...nel.org>,
        "'Sascha Hauer'" <s.hauer@...gutronix.de>,
        "'Pengutronix Kernel Team'" <kernel@...gutronix.de>,
        "'NXP Linux Team'" <linux-imx@....com>,
        "'Lorenzo Pieralisi'" <lorenzo.pieralisi@....com>,
        "'Andrew Murray'" <amurray@...goodpenguin.co.uk>,
        <linux-pci@...r.kernel.org>,
        "'moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE'" 
        <linux-arm-kernel@...ts.infradead.org>,
        "'linux-kernel'" <linux-kernel@...r.kernel.org>
Subject: R: [PATCH 2/4] drivers: pci: dwc: pci-imx6: update binding to generic name

> Hi Ansuel,
> 
> On Fri, Apr 10, 2020 at 8:07 AM <ansuelsmth@...il.com> wrote:
> 
> > so no chance of changing this?
> 
> Reading the commit log I don't see any explanation as to why you need
> to change the current bindings.
> 
> What is the motivation for doing this? Is this really worth it?

It's really to not have the same exact binding to 2 different driver.
If this would cause problem I will use qcom,tx-deemph...... but still it looks
wrong to me having this. How should I proceed?