All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <Joao.Pinto@synopsys.com>
Cc: <andrew@lunn.ch>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 net-next] net: stmmac: add drop transmit status feature
Date: Wed, 12 Apr 2017 16:43:38 +0100	[thread overview]
Message-ID: <47a1103e-74da-91be-eb9d-ad772b6a2e1f@synopsys.com> (raw)
In-Reply-To: <20170412.112825.1170167825508436176.davem@davemloft.net>

Às 4:28 PM de 4/12/2017, David Miller escreveu:
> From: Joao Pinto <Joao.Pinto@synopsys.com>
> Date: Wed, 12 Apr 2017 16:13:33 +0100
> 
>> Às 3:51 PM de 4/12/2017, David Miller escreveu:
>>> You cannot develop performance based features and only test their
>>> impact on FPGA when almost all users are on real silicon.
>>>
>>> And this requirement is absolutely non-negotiable.
>>>
>>> You must test the impact on real silicon otherwise your performance
>>> numbers, which are required to be provided in the commit message
>>> for any "performance" feature or change, are completely useless.
>>
>> Next time I won't mention anything about performance, honestly. "Drop TX Status"
>> is just an IP Core feature that can or not be used, it is up to the driver user.
> 
> Being dishonest about why a change might be desirable doesn't help things, in fact
> now that you've stated this intent in the future, people know to be suspucious of
> your changes.

Dishonest? I just sent the patch adding a optional configuration that can boost
performance in applications where timestapping is not an issue. You can request
more info in stmmac.txt, but calling me dishonest is a bit out of line.

I perfectly accept if you feel that the patch is not useful, that's fine.

> 
> I seriously don't think you realize the ramifications of what you just said right
> there.

No, I don't see honestly. I just said that I am a developer that has an interest
in the success of stmmac, but I don't want to steal maintenance seats :).

> 
> Everything here is about trust, and if you create a situation where you can't be
> trusted then the process of doing upstream development will be extremely difficult
> and time consuming for you.

Agree, trust is fundamental. I never gave reasons not to be trusted, in fact I
have a good relation with some of the stmmac developers and in other subsystems,
so I don't see the point of your observations.

> 
> Thanks.
> 

Joao

  reply	other threads:[~2017-04-12 15:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:26 [PATCH v2 net-next] net: stmmac: add drop transmit status feature Joao Pinto
2017-04-12 11:56 ` Andrew Lunn
2017-04-12 12:07   ` Joao Pinto
2017-04-12 13:10     ` Andrew Lunn
2017-04-12 13:16       ` Joao Pinto
2017-04-12 13:52         ` Andrew Lunn
2017-04-12 13:55           ` Joao Pinto
2017-04-12 14:51             ` David Miller
2017-04-12 15:13               ` Joao Pinto
2017-04-12 15:28                 ` David Miller
2017-04-12 15:43                   ` Joao Pinto [this message]
2017-04-12 16:03                     ` David Miller
2017-04-12 14:58     ` Andrew Lunn
2017-04-12 17:43       ` Florian Fainelli
2017-04-18 10:25         ` Joao Pinto

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=47a1103e-74da-91be-eb9d-ad772b6a2e1f@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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.