All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>
Cc: hkallweit1@gmail.com, f.fainelli@gmail.com, rjui@broadcom.com,
	sbranden@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: set 1Gbps as default for driver features
Date: Wed, 19 Dec 2018 10:21:57 +0100	[thread overview]
Message-ID: <20181219092157.GC14923@lunn.ch> (raw)
In-Reply-To: <20181218.214656.347202577049617540.davem@davemloft.net>

On Tue, Dec 18, 2018 at 09:46:56PM -0800, David Miller wrote:
> From: Heiner Kallweit <hkallweit1@gmail.com>
> Date: Tue, 18 Dec 2018 19:09:36 +0100
> 
> > Eventually defining 1Gbps as default isn’t something we would need to roll
> > back later once PHYs above 1Gbps are the standard. We can deal with this in
> > phylib w/o affecting existing drivers. Therefore I think the proposed change
> > is future-proof.
> 
> Andrew, what do you think given Heiner's explanation of his thinking?

Ah, sorry, i replied P2P to Heiner and Florian. Please give us a bit
of time to discuss this, we can let you know before net-next closes.

   Andrew

  reply	other threads:[~2018-12-19  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18  6:34 [PATCH net-next 0/2] net: phy: set 1Gbps as default for driver features Heiner Kallweit
2018-12-18  6:36 ` [PATCH net-next 1/2] " Heiner Kallweit
2018-12-18  6:39 ` [PATCH net-next 2/2] net: phy: remove feature definition from 1Gbps PHY drivers Heiner Kallweit
2018-12-18  9:39 ` [PATCH net-next 0/2] net: phy: set 1Gbps as default for driver features Andrew Lunn
2018-12-18 18:09   ` Heiner Kallweit
2018-12-19  5:46     ` David Miller
2018-12-19  9:21       ` Andrew Lunn [this message]
2018-12-19 19:30         ` Heiner Kallweit
2018-12-19 19:34           ` 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=20181219092157.GC14923@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.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 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.