linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	kernel@pengutronix.de, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	Fabio Estevam <festevam@gmail.com>,
	David Jander <david@protonic.nl>,
	Russell King <linux@armlinux.org.uk>,
	Philippe Schenker <philippe.schenker@toradex.com>
Subject: Re: [PATCH v2 0/7] remove different PHY fixups
Date: Mon, 29 Mar 2021 10:13:32 +0200	[thread overview]
Message-ID: <20210329081332.oa7a7o7uhywawqqj@pengutronix.de> (raw)
In-Reply-To: <20210329004458.GD22955@dragon>

On Mon, Mar 29, 2021 at 08:44:59AM +0800, Shawn Guo wrote:
> On Wed, Mar 24, 2021 at 06:54:24AM +0100, Oleksij Rempel wrote:
> > Hi Shawn,
> > 
> > ping, do this patches need some ACK from some one?
> 
> As this will break existing DTBs, I need more ACKs from people to see
> the consensus that this is the right thing to do.

Do you need ACKs from some concrete people?

Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2021-03-29  8:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 11:26 [PATCH v2 0/7] remove different PHY fixups Oleksij Rempel
2021-03-09 11:26 ` [PATCH v2 1/7] ARM: imx6q: remove PHY fixup for KSZ9031 Oleksij Rempel
2021-05-11  1:49   ` Shawn Guo
2021-03-09 11:26 ` [PATCH v2 2/7] ARM: imx6q: remove TX clock delay of ar8031_phy_fixup() Oleksij Rempel
2021-03-09 11:26 ` [PATCH v2 3/7] ARM: imx6q: remove hand crafted PHY power up in ar8035_phy_fixup() Oleksij Rempel
2021-03-09 11:26 ` [PATCH v2 4/7] ARM: imx6q: remove clk-out fixup for the Atheros AR8031 and AR8035 PHYs Oleksij Rempel
2021-03-09 11:26 ` [PATCH v2 5/7] ARM: imx6q: remove Atheros AR8035 SmartEEE fixup Oleksij Rempel
2021-03-09 11:26 ` [PATCH v2 6/7] ARM: imx6sx: remove Atheros AR8031 PHY fixup Oleksij Rempel
2021-03-09 11:26 ` [PATCH v2 7/7] ARM: imx7d: " Oleksij Rempel
2021-03-24  5:54 ` [PATCH v2 0/7] remove different PHY fixups Oleksij Rempel
2021-03-29  0:44   ` Shawn Guo
2021-03-29  8:13     ` Oleksij Rempel [this message]
2021-03-30 14:00 ` Fabio Estevam
2021-03-30 14:30   ` Andrew Lunn
2021-03-30 15:04     ` Fabio Estevam
2021-04-13  9:43       ` Oleksij Rempel
2021-04-13 10:00 ` Lucas Stach
2021-04-13 10:51   ` Russell King - ARM Linux admin
2021-04-13 11:10     ` Lucas Stach

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=20210329081332.oa7a7o7uhywawqqj@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=david@protonic.nl \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=philippe.schenker@toradex.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).