From: Florian Fainelli <f.fainelli@gmail.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixed_phy: pass 'irq' to fixed_phy_add()
Date: Thu, 03 Sep 2015 13:23:49 -0700 [thread overview]
Message-ID: <55E8AC55.9080105@gmail.com> (raw)
In-Reply-To: <3613326.r1qXWqo08b@wasted.cogentembedded.com>
On 03/09/15 13:22, Sergei Shtylyov wrote:
> I've noticed that fixed_phy_register() ignores its 'irq' parameter instead of
> passing it to fixed_phy_add(). Luckily, fixed_phy_register() seems to always
> be called with PHY_POLL for 'irq'... :-)
So not critical for -stable, good!
>
> Fixes: a75951217472 ("net: phy: extend fixed driver with fixed_phy_register()")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2015-09-03 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 20:22 [PATCH] fixed_phy: pass 'irq' to fixed_phy_add() Sergei Shtylyov
2015-09-03 20:23 ` Florian Fainelli [this message]
2015-09-07 6:49 ` David Miller
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=55E8AC55.9080105@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).