From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] Added SIOCSMIIREG (mii write) support to intel igb driver
Date: Mon, 26 Jun 2017 14:11:52 -0700 [thread overview]
Message-ID: <1498511512.3237.7.camel@intel.com> (raw)
In-Reply-To: <20170622132356.2567-1-michael.moese@men.de>
On Thu, 2017-06-22 at 15:23 +0200, Michael Moese wrote:
> From: Andreas Werner <andreas.werner@men.de>
>
> Signed-off-by: Andreas Werner <andreas.werner@men.de>
> ---
> ?drivers/net/ethernet/intel/igb/igb_main.c | 4 ++++
> ?1 file changed, 4 insertions(+)
NACK
Why? Your lack of patch description does not provide a reasoning on why we
need this change. I need a patch description that provides justification
on why we need this change, before I add this to my queue for testing and
acceptance upstream.
Please resubmit with the requested information/change.
>
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c
> b/drivers/net/ethernet/intel/igb/igb_main.c
> index 1cf74aa4ebd9..87e496eeefb1 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -7716,6 +7716,10 @@ static int igb_mii_ioctl(struct net_device
> *netdev, struct ifreq *ifr, int cmd)
> ? return -EIO;
> ? break;
> ? case SIOCSMIIREG:
> + if (igb_write_phy_reg(&adapter->hw, data->reg_num &
> 0x1F,
> + ??????data->val_in))
> + return -EIO;
> + break;
> ? default:
> ? return -EOPNOTSUPP;
> ? }
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170626/1ff7d9df/attachment-0001.asc>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Michael Moese <michael.moese@men.de>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andreas Werner <andreas.werner@men.de>
Subject: Re: [PATCH] Added SIOCSMIIREG (mii write) support to intel igb driver
Date: Mon, 26 Jun 2017 14:11:52 -0700 [thread overview]
Message-ID: <1498511512.3237.7.camel@intel.com> (raw)
In-Reply-To: <20170622132356.2567-1-michael.moese@men.de>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
On Thu, 2017-06-22 at 15:23 +0200, Michael Moese wrote:
> From: Andreas Werner <andreas.werner@men.de>
>
> Signed-off-by: Andreas Werner <andreas.werner@men.de>
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 4 ++++
> 1 file changed, 4 insertions(+)
NACK
Why? Your lack of patch description does not provide a reasoning on why we
need this change. I need a patch description that provides justification
on why we need this change, before I add this to my queue for testing and
acceptance upstream.
Please resubmit with the requested information/change.
>
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c
> b/drivers/net/ethernet/intel/igb/igb_main.c
> index 1cf74aa4ebd9..87e496eeefb1 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -7716,6 +7716,10 @@ static int igb_mii_ioctl(struct net_device
> *netdev, struct ifreq *ifr, int cmd)
> return -EIO;
> break;
> case SIOCSMIIREG:
> + if (igb_write_phy_reg(&adapter->hw, data->reg_num &
> 0x1F,
> + data->val_in))
> + return -EIO;
> + break;
> default:
> return -EOPNOTSUPP;
> }
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-26 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 13:23 [Intel-wired-lan] [PATCH] Added SIOCSMIIREG (mii write) support to intel igb driver Michael Moese
2017-06-22 13:23 ` Michael Moese
2017-06-26 21:11 ` Jeff Kirsher [this message]
2017-06-26 21:11 ` Jeff Kirsher
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=1498511512.3237.7.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.