From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, andrew@lunn.ch, l.stach@pengutronix.de,
fugang.duan@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: fec: Fix unbalanced PM runtime calls
Date: Sun, 18 Mar 2018 20:12:28 -0400 (EDT) [thread overview]
Message-ID: <20180318.201228.2201277107982982829.davem@davemloft.net> (raw)
In-Reply-To: <f1ba3f3e-adef-c7f0-d9b2-47bbdade91f5@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Sun, 18 Mar 2018 14:42:22 -0700
> On 03/18/2018 01:35 PM, David Miller wrote:
>> Queue this up for -stable?
>
> I would be inclined to say yes, it was not exactly easy to track down a
> set of commits, since this was changed quite a bit.
Ok, queued up.
prev parent reply other threads:[~2018-03-19 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 19:49 [PATCH net] net: fec: Fix unbalanced PM runtime calls Florian Fainelli
2018-03-18 20:35 ` David Miller
2018-03-18 21:42 ` Florian Fainelli
2018-03-19 0:12 ` 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=20180318.201228.2201277107982982829.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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).