Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <6687de05226dd055ee362933d4841a12b038792d.1601655904.git.npcomplete13@gmail.com>
 <20201104202952.783724-1-npcomplete13@gmail.com> <20201104202952.783724-2-npcomplete13@gmail.com>
In-Reply-To: <20201104202952.783724-2-npcomplete13@gmail.com>
From:   =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= <zajec5@gmail.com>
Date:   Mon, 9 Nov 2020 18:21:45 +0100
Message-ID: <CACna6ryJ70PepwE1u-kUqjKWbae6F=Gp2Scoe2pHtaGuJvqacA@mail.gmail.com>
Subject: Re: [PATCH v2 1/2] ARM: dts: BCM5301X: pinctrl - use correct driver
 and define mdio pins
To:     Vivek Unune <npcomplete13@gmail.com>
Cc:     florian.fainelli@broadcom.com, Hauke Mehrtens <hauke@hauke-m.de>,
        bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
        Rob Herring <robh+dt@kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, 4 Nov 2020 at 21:30, Vivek Unune <npcomplete13@gmail.com> wrote:
> BCM47094 version of pinmux uses different driver and supports mdio
> pinmux pins. Hence, use the correct driver and define the pins.
>
> Signed-off-by: Vivek Unune <npcomplete13@gmail.com>

Subject and message are a bit confusing as it's actually a matter of
chipset specific binding and not a driver.

Change looks OK, thanks for handling that!

Acked-by: Rafa=C5=82 Mi=C5=82ecki <rafal@milecki.pl>