[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGVrzcZ8vXBn4omyR7+ejihhcrspt-Rz_BBh55esxNFO06gHgQ@mail.gmail.com>
Date: Thu, 10 Apr 2014 21:55:29 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: netdev <netdev@...r.kernel.org>,
Randy Dunlap <rdunlap@...radead.org>,
Jonathan Cameron <jic23@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Prabhakar Lad <prabhakar.csengg@...il.com>,
santosh.shilimkar@...com, Sekhar Nori <nsekhar@...com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dlos <davinci-linux-open-source@...ux.davincidsp.com>
Subject: Re: [PATCH 0/2] introduce devm_mdiobus_alloc/devm_mdiobus_free
Hi Grygorii,
2014-04-04 6:40 GMT-07:00 Grygorii Strashko <grygorii.strashko@...com>:
> Introduce a resource managed devm_mdiobus_alloc()/devm_mdiobus_free()
> to automatically clean up MDIO bus alocations made by MDIO drivers,
> thus leading to simplified MDIO drivers code.
>
> Update Davinci MDIO driver ss example of new devm APIs usage.
This does look good at first glance. net-next is currently closed at
the moment, so this will have to be merged later.
At some point, we might also want to handle the mdio_bus irq array, as
that one is also usually dynamically allocated. Maybe we could just do
a static irq[PHY_MAX_ADDR] allocation, 32 times the size of an integer
might not be worth a potential leak.
>
> Grygorii Strashko (2):
> mdio_bus: implement devm_mdiobus_alloc/devm_mdiobus_free
> net: davinci_mdio: use devm_* api
>
> Documentation/driver-model/devres.txt | 4 ++
> drivers/net/ethernet/ti/davinci_mdio.c | 21 ++--------
> drivers/net/phy/mdio_bus.c | 68 ++++++++++++++++++++++++++++++++
> include/linux/phy.h | 2 +
> 4 files changed, 78 insertions(+), 17 deletions(-)
>
> --
> 1.7.9.5
>
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists