[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200323.220026.1402203457473336218.davem@davemloft.net>
Date: Mon, 23 Mar 2020 22:00:26 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: zhengdejin5@...il.com
Cc: andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com,
linux@...linux.org.uk, corbet@....net, tglx@...utronix.de,
gregkh@...uxfoundation.org, allison@...utok.net,
mchehab+samsung@...nel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v7 00/10] introduce read_poll_timeout
From: Dejin Zheng <zhengdejin5@...il.com>
Date: Mon, 23 Mar 2020 23:05:50 +0800
> This patch sets is introduce read_poll_timeout macro, it is an extension
> of readx_poll_timeout macro. the accessor function op just supports only
> one parameter in the readx_poll_timeout macro, but this macro can
> supports multiple variable parameters for it. so functions like
> phy_read(struct phy_device *phydev, u32 regnum) and
> phy_read_mmd(struct phy_device *phydev, int devad, u32 regnum) can
> use this poll timeout framework.
>
> the first patch introduce read_poll_timeout macro, and the second patch
> redefined readx_poll_timeout macro by read_poll_timeout(), and the other
> patches are examples using read_poll_timeout macro.
...
Series applied, thanks.
Powered by blists - more mailing lists