mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Sune Mølgaard" <sune@molgaard.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Summarizing deprecations
Date: Mon, 2 Jun 2014 17:15:44 -0700	[thread overview]
Message-ID: <20140603001544.GB17821@kroah.com> (raw)
In-Reply-To: <538D04D4.1060906@molgaard.org>

On Tue, Jun 03, 2014 at 01:12:20AM +0200, Sune Mølgaard wrote:
> Hi again, and thank you still for interacting,
> 
> Greg KH wrote:
> > What specific drivers are they?  Why are the drivers out of the tree?
> > I'll gladly add them to the drivers/staging/ directory as long as the
> > license of them allows me to do so.  That way api changes will happen
> > automatically for them.
> 
> For at least one of the manufacturers, I have already pointed them in
> your direction with regards to the previously mentioned project. They
> lamented that they would love to take you up on your offer, but that
> their legal department was less than enthusiastic, based on fear of
> repercussions from their chip suppliers.
> 
> This particular company could be a candidate for positive nudging from
> stronger entities than myself, as just one guy.

Feel free to follow up with me about this company and contacts
privately, if you feel I can help out there.

> It stands to reason, though, that there may not only be legal obstacles
> to supporting OSS drivers, but also that corporate resources allocated
> to keeping their "monstrosity" current may be severely lacking.

Take away the legal issues (their side, not ours), and then merge the
driver into the kernel and then all of those maintenance issues go
away for the most part, allowing a single developer to just baby-sit the
driver to ensure nothing goes wrong on newer kernel releases.

That's the Linux kernel development model, it's worked really well for
the past 20+ years, creating something that works on more hardware than
any other operating system ever has, so we must be doing something right
here with the model :)

greg k-h

  reply	other threads:[~2014-06-03  0:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  2:04 Sune Mølgaard
2014-05-31  2:21 ` Greg KH
2014-05-31  2:56   ` Sune Mølgaard
2014-05-31  3:37     ` Greg KH
2014-06-02 23:12       ` Sune Mølgaard
2014-06-03  0:15         ` Greg KH [this message]
2014-05-31  3:00 ` Steven Rostedt

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=20140603001544.GB17821@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sune@molgaard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®