From: "Rafał Miłecki" <zajec5@gmail.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: "Kishon Vijay Abraham I" <kishon@ti.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, "Hauke Mehrtens" <hauke@hauke-m.de>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] phy: phy-bcm-ns-usb3: drop support for deprecated DT binding
Date: Thu, 19 Nov 2020 08:55:48 +0100 [thread overview]
Message-ID: <CACna6ryH6Ptdbs25Uv_ySYRXTaWsG4+dz2LD-5=By1_31VWEyQ@mail.gmail.com> (raw)
In-Reply-To: <20201119062720.GE50232@vkoul-mobl>
On Thu, 19 Nov 2020 at 07:27, Vinod Koul <vkoul@kernel.org> wrote:
> On 13-11-20, 12:34, Rafał Miłecki wrote:
> > From: Rafał Miłecki <rafal@milecki.pl>
> >
> > Initially this PHY driver was implementing MDIO access on its own. It
> > was caused by lack of proper hardware design understanding.
> >
> > It has been changed back in 2017. DT bindings were changed and driver
> > was updated to use MDIO layer.
> >
> > It should be really safe now to drop the old deprecated code. All Linux
> > stored DT files don't use it for 3,5 year. There is close to 0 chance
> > there is any bootloader with its own DTB using old the binding.
>
> Applied, thanks
>
> While applying, it gave me a minor conflict, please do check the
> resolution
Oops, I used your master branch instead of next. Waiting for your push :)
--
Rafał
next prev parent reply other threads:[~2020-11-19 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 11:34 [PATCH] phy: phy-bcm-ns-usb3: drop support for deprecated DT binding Rafał Miłecki
2020-11-13 23:13 ` Florian Fainelli
2020-11-19 6:27 ` Vinod Koul
2020-11-19 7:55 ` Rafał Miłecki [this message]
2020-11-19 8:24 ` Rafał Miłecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACna6ryH6Ptdbs25Uv_ySYRXTaWsG4+dz2LD-5=By1_31VWEyQ@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).