From: David Miller <davem@davemloft.net>
To: festevam@gmail.com
Cc: rmk+kernel@arm.linux.org.uk, Frank.Li@freescale.com,
netdev@vger.kernel.org, fabio.estevam@freescale.com
Subject: Re: [PATCH net-next] fec: Fix fec_enet_alloc_buffers() error path
Date: Mon, 06 Oct 2014 00:54:21 -0400 (EDT) [thread overview]
Message-ID: <20141006.005421.1323921175700971872.davem@davemloft.net> (raw)
In-Reply-To: <1412440801-15381-1-git-send-email-festevam@gmail.com>
From: Fabio Estevam <festevam@gmail.com>
Date: Sat, 4 Oct 2014 13:40:01 -0300
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> When fec_enet_alloc_buffers() fails we should better undo the previous actions,
> which consists of: disabling the FEC clocks and putting the FEC pins into
> inactive state.
>
> The error path for fec_enet_mii_probe() is kept unchanged.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Applied, thanks Fabio.
prev parent reply other threads:[~2014-10-06 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 16:40 [PATCH net-next] fec: Fix fec_enet_alloc_buffers() error path Fabio Estevam
2014-10-06 4:54 ` 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=20141006.005421.1323921175700971872.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Frank.Li@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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).