mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Greg KH <greg@kroah.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jouni Malinen <j@w1.fi>, Sujith <m.sujith@gmail.com>,
	Sujith <Sujith.Manoharan@atheros.com>,
	Senthilkumar Balasubramanian 
	<Senthilkumar.Balasubramanian@atheros.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Christoph Hellwig <hch@infradead.org>,
	Vasanthakumar Thiagarajan <vasanth@atheros.com>
Subject: Re: Staging, place holder for better company/community development  model
Date: Mon, 9 Mar 2009 00:02:30 +0100	[thread overview]
Message-ID: <c384c5ea0903081602j5d8a91b7pad5eec80fffd3274@mail.gmail.com> (raw)
In-Reply-To: <43e72e890903022314o44ae710u834d6207403fd4a2@mail.gmail.com>

Hello,

On Tue, Mar 3, 2009 at 8:14 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>
> With future devices we may want to create a better path for
> integration into upstream drivers. But I also want users to get
> support for the devices as soon as those devices hit shelves in the
> market, maybe even before.
>
The situation prior to the staging/ tree, was that niche drivers often
lived outside of the kernel tree, without much exposure and without
API consistency.

With staging/ available, there should be no reason for either a
company or individual(s) to develop a Linux driver outside the kernel
tree.

A driver can live there until enough momentum (devices in the field,
in Linux developer hands) exists to have the driver reworked for main
tree clearance.

At least, with this in the back of my head I submitted my driver to
staging which would otherwise live in a secret place. I have contacted
the hardware vendor and they are (not yet) interested in Linux
support. I am counting the days before they will.

Regards,
-- 
Leon

      parent reply	other threads:[~2009-03-08 23:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  7:14 Luis R. Rodriguez
2009-03-03  7:30 ` Greg KH
2009-03-03  7:45   ` Luis R. Rodriguez
2009-03-03 15:56     ` Greg KH
2009-03-08 12:07 ` Johannes Berg
2009-03-08 22:33   ` Greg KH
2009-03-09  7:21     ` Johannes Berg
2009-03-09 19:41       ` Greg KH
2009-03-09 21:20         ` Johannes Berg
2009-03-11  5:00           ` Greg KH
2009-03-11  9:08             ` Johannes Berg
2009-03-11 16:02               ` Greg KH
2009-03-11 19:33                 ` J.R. Mauro
2009-04-07 23:15                   ` Greg KH
2009-03-08 23:02 ` Leon Woestenberg [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=c384c5ea0903081602j5d8a91b7pad5eec80fffd3274@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=Senthilkumar.Balasubramanian@atheros.com \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m.sujith@gmail.com \
    --cc=mcgrof@gmail.com \
    --cc=vasanth@atheros.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 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®