linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: gregkh@linuxfoundation.org
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, aaro.koskinen@iki.fi, nevola@gmail.com,
	tremyfr@gmail.com, asbjorn@asbjorn.st, jarod@redhat.com,
	bhaktipriya96@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: Call SET_NETDEV_DEV()
Date: Tue, 27 Dec 2016 14:15:57 -0800	[thread overview]
Message-ID: <748b758b-7a9c-d58e-2fa5-52b6fa031ae3@gmail.com> (raw)
In-Reply-To: <20161220.222020.1448709395205678279.davem@davemloft.net>

On 12/20/2016 07:20 PM, David Miller wrote:
> From: Florian Fainelli <f.fainelli@gmail.com>
> Date: Tue, 20 Dec 2016 17:02:37 -0800
> 
>> On 12/14/2016 05:13 PM, Florian Fainelli wrote:
>>> The Octeon driver calls into PHYLIB which now checks for
>>> net_device->dev.parent, so make sure we do set it before calling into
>>> any MDIO/PHYLIB related function.
>>>
>>> Fixes: ec988ad78ed6 ("phy: Don't increment MDIO bus refcount unless it's a different owner")
>>> Reported-by: Aaro Koskinen <aaro.koskinen@iki.fi>
>>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>>
>> Greg, David, since this is a fix for a regression introduced in the net
>> tree, it may make sense that David take it via his tree.
> 
> Since the change in question is in Linus's tree, it's equally valid
> for Greg to take it as well.

Sure, Greg, can you take this change? Thank you!
-- 
Florian

  reply	other threads:[~2016-12-27 22:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  1:13 [PATCH] staging: octeon: Call SET_NETDEV_DEV() Florian Fainelli
2016-12-21  1:02 ` Florian Fainelli
2016-12-21  3:20   ` David Miller
2016-12-27 22:15     ` Florian Fainelli [this message]
2017-01-03 16:11       ` Greg KH

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=748b758b-7a9c-d58e-2fa5-52b6fa031ae3@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=asbjorn@asbjorn.st \
    --cc=bhaktipriya96@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarod@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nevola@gmail.com \
    --cc=tremyfr@gmail.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).