netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: florian@openwrt.org
Cc: netdev@vger.kernel.org, konszert@marvell.com, afleming@gmail.com
Subject: Re: [RFC PATCH] net: phy: remove flags argument from phy_{attach,connect,connect_direct}
Date: Fri, 11 Jan 2013 19:47:29 -0800 (PST)	[thread overview]
Message-ID: <20130111.194729.1404456884791637120.davem@davemloft.net> (raw)
In-Reply-To: <1357903907-16049-1-git-send-email-florian@openwrt.org>

From: Florian Fainelli <florian@openwrt.org>
Date: Fri, 11 Jan 2013 12:31:47 +0100

> The flags argument of the phy_{attach,connect,connect_direct} functions
> is used to assign a struct phy_device dev_flags with the value passed.
> All callers but the tg3 driver pass the flag 0, which results in the
> underlying PHY drivers in drivers/net/phy/ not being able to actually
> use any of the flags they would check in dev_flags. This patch gets rid of
> the flags argument, and passes phydev->dev_flags to the internal PHY
> library call phy_attach_direct() such that drivers which actually modify
> a phy device dev_flags get the value preserved for use by the underly
> phy driver.
> 
> Signed-off-by: Florian Fainelli <florian@openwrt.org>

This change is fine, except for this part:

> diff --git a/include/linux/version.h b/include/linux/version.h
> new file mode 100644
> index 0000000..0c8c321
> --- /dev/null
> +++ b/include/linux/version.h
> @@ -0,0 +1,2 @@
> +#define LINUX_VERSION_CODE 197120
> +#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

  reply	other threads:[~2013-01-12  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 11:31 [RFC PATCH] net: phy: remove flags argument from phy_{attach,connect,connect_direct} Florian Fainelli
2013-01-12  3:47 ` David Miller [this message]
2013-01-13  8:54 ` Kosta Zertsekel

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=20130111.194729.1404456884791637120.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=afleming@gmail.com \
    --cc=florian@openwrt.org \
    --cc=konszert@marvell.com \
    --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).