From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Andrew Lunn <andrew@lunn.ch>,
Linux kernel netdev mailing list <netdev@vger.kernel.org>
Subject: Re: confusing comment, explanation of @IFF_RUNNING in if.h
Date: Mon, 27 Aug 2018 04:04:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1808270403420.22848@localhost.localdomain> (raw)
In-Reply-To: <5c3004dc-e877-c142-60ac-91f4623e5153@hartkopp.net>
On Mon, 27 Aug 2018, Oliver Hartkopp wrote:
> "released upon production" means usually: Oh, we put that driver in
> a tar-ball on a CD that's shipped with the product and which will
> get no further visibility nor (security) maintenance.
>
> Robert, please tell your manager that creating a driver is no rocket
> science and also brings no "costumer differentiation" which needs to
> be covered under NDA.
>
> Posting drivers and bring it into mainline Linux heavily increases
> the quality due to the review process and all the people that are
> willing to help you to get better. At the end your driver gets
> long-term maintenance and other people can benefit from it - as your
> boss is getting benefit from using Linux right now.
>
> When something is "released upon production" it will not be in a
> quality that it could go into the kernel - and no one will have the
> time/money/ambition to spend effort on it then. You have just
> produced one of the numerous dead out-of-tree drivers. That would be
> just sad.
i make these arguments on a regular basis with all of my clients
but, as a contractor, i have little influence. but i will continue to
make them.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2018-08-27 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 8:13 confusing comment, explanation of @IFF_RUNNING in if.h Robert P. J. Day
2018-08-26 19:20 ` Andrew Lunn
2018-08-26 19:20 ` Robert P. J. Day
2018-08-26 19:28 ` Andrew Lunn
2018-08-26 19:30 ` Robert P. J. Day
2018-08-26 20:51 ` Stephen Hemminger
2018-08-27 6:20 ` Robert P. J. Day
2018-08-27 7:11 ` Oliver Hartkopp
2018-08-27 8:04 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1808270403420.22848@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=stephen@networkplumber.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.