[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1342885066.11373.126.camel@deadeye.wl.decadent.org.uk>
Date: Sat, 21 Jul 2012 16:37:46 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
CC: Jeff Kirsher <jeffrey.t.kirsher@...el.com>, <davem@...emloft.net>,
<netdev@...r.kernel.org>, <gospo@...hat.com>,
<sassmann@...hat.com>, Tushar Dave <tushar.n.dave@...el.com>
Subject: Re: [net-next 4/6] e1000: configure and read MDI settings
On Fri, 2012-07-20 at 18:17 -0700, Brandeburg, Jesse wrote:
>
> On Fri, 20 Jul 2012, Ben Hutchings wrote:
> > Why don't you set ecmd->eth_tp_mdix_ctrl here?
> >
> > If you also leave it as 0, it's impossible for userland to tell whether
> > the current mode was forced or automatically selected.
>
> Thanks for the review, right now the get interface (and ethtool display)
> doesn't support any way to report if the setting was forced or not. I
> didn't think about changing the get because I didn't want to modify the
> userland reporting (I also figured it was a simple interface right now,
> and didn't need changing, and was focused on the _set_ which is the part
> fixing the users' reported bugs.)
Everything else you can change with ETHTOOL_SSET is also reported by
ETHTOOL_GSET; why would this be any different?
> I think the patches as they currently stand are okay, do you agree? I
> would be glad to submit a followon to implement the new "get" interface if
> we can hash out the interface changes, but I see no reason to gate these
> patches.
You left this for 20 months, what's the hurry now?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists