[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171115211227.GE29642@lunn.ch>
Date: Wed, 15 Nov 2017 22:12:27 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Marc Gonzalez <marc_gonzalez@...madesigns.com>
Cc: Mans Rullgard <mans@...sr.com>,
Florian Fainelli <f.fainelli@...il.com>,
Mason <slash.tmp@...e.fr>, netdev <netdev@...r.kernel.org>,
Thibaud Cornic <thibaud_cornic@...madesigns.com>,
David Miller <davem@...emloft.net>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 2/4] net: nb8800: Simplify nb8800_pause_config()
On Wed, Nov 15, 2017 at 04:19:56PM +0100, Marc Gonzalez wrote:
> On 15/11/2017 16:03, Andrew Lunn wrote:
>
> > On Wed, Nov 15, 2017 at 03:33:47PM +0100, Marc Gonzalez wrote:
> >
> >> On 15/11/2017 15:17, Andrew Lunn wrote:
> >>
> >> In our local branch, I have completely disabled flow control support,
> >> so I don't have to worry about this problem.
> >
> > That is an interesting statement. You now know there is an issue here,
> > your solution is to fix your private branch and leave mainline as is.
>
> All my patches are NACKed, what would you have me do?
Hi Marc
You need to consider your own maintenance burden. You want your local
branch to be as near to mainline as possible. Each change you have
means additional maintenance work for you. It also possibly means
additional work for your customers.
You seem to think flow control in your hardware is too broken to be
usable. So you probably want to submit a patch to mainline disabling
it. If it is accepted, that is one less patch you need to maintain.
Andrew
Powered by blists - more mailing lists