From: Andy Fleming <afleming@freescale.com>
To: Rini van Zetten <rini@arvoo.nl>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]drivers/net/phy/: default return value in ioctl phy.c
Date: Mon, 14 Jan 2008 12:48:21 -0600 [thread overview]
Message-ID: <E7E3FE26-AD70-4660-9D5E-7A6FCEC67127@freescale.com> (raw)
In-Reply-To: <014901c83c06$da9223e0$2b00a8c0@ARV127>
On Dec 11, 2007, at 09:02, Rini van Zetten wrote:
> Hello Andy,
>
> This patch (to 2.6.23.9) add a default return value EOPNOTSUPP to
> the ioctl function. The problem with the always 0 return value is
> that the iwconfig (wireless) tool found a valid device when an
> ethernet device uses the phy abstraction layer.
> I 've tetsted this with the macb driver.
>
>
> Signed-off-by: Rini van Zetten <rini@arvoo.nl>
Acked-by: Andy Fleming <afleming@freescale.com>
prev parent reply other threads:[~2008-01-14 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 15:02 [PATCH]drivers/net/phy/: default return value in ioctl phy.c Rini van Zetten
2008-01-14 18:48 ` Andy Fleming [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=E7E3FE26-AD70-4660-9D5E-7A6FCEC67127@freescale.com \
--to=afleming@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rini@arvoo.nl \
/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).