From: David Miller <davem@davemloft.net>
To: sebastian.hesselbarth@gmail.com
Cc: andrew@lunn.ch, jason@lakedaemon.net,
sergei.shtylyov@cogentembedded.com, linux-doc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
paulus@samba.org, rob@landley.net, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, florian@openwrt.org,
buytenh@wantstofly.org
Subject: Re: [PATCH 0/2] net: mv643xx_eth: use managed clk and allocation
Date: Thu, 11 Apr 2013 16:20:07 -0400 (EDT) [thread overview]
Message-ID: <20130411.162007.896982847089316512.davem@davemloft.net> (raw)
In-Reply-To: <1365672574-31123-1-git-send-email-sebastian.hesselbarth@gmail.com>
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Date: Thu, 11 Apr 2013 11:29:32 +0200
> With introduction of common clock framework and the ability to provide
> gated clocks, mv643xx_eth required calls to get and enable these clock
> gates on some platforms. Back then, common clock framework api wasn't
> safe for architectures without support for common clocks. This has
> changed now and there are also managed (devm_) counterparts for clock
> related functions.
>
> The second patch in this series, also converts kzalloc to devm_kzalloc
> where applicable.
>
> Both patches have been sent to the corresponding mailing lists as
> individual patches before. To get the order required to apply them right,
> this patch set combines both patches into one set.
Both applied to net-next, thanks.
prev parent reply other threads:[~2013-04-11 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 9:29 [PATCH 0/2] net: mv643xx_eth: use managed clk and allocation Sebastian Hesselbarth
2013-04-11 9:29 ` [PATCH 1/2] net: mv643xx_eth: add shared clk and cleanup existing clk handling Sebastian Hesselbarth
2013-04-11 9:29 ` [PATCH v2 2/2] net: mv643xx_eth: use managed devm_kzalloc Sebastian Hesselbarth
2013-04-11 9:32 ` [PATCH 0/2] net: mv643xx_eth: use managed clk and allocation Florian Fainelli
2013-04-11 20:20 ` David Miller [this message]
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=20130411.162007.896982847089316512.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=buytenh@wantstofly.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=florian@openwrt.org \
--cc=jason@lakedaemon.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
/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).