From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
badhri@google.com, Oliver Neukum <oneukum@suse.com>,
Mats Karrman <mats.dev.list@gmail.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
linux-usb@vger.kernel.org
Subject: Re: typec: tcpm/tcpci drivers acceptable for drivers/staging in v4.12 ?
Date: Tue, 25 Apr 2017 10:54:02 -0700 [thread overview]
Message-ID: <20170425175402.GA28665@roeck-us.net> (raw)
In-Reply-To: <20170425173742.GA20305@kroah.com>
On Tue, Apr 25, 2017 at 07:37:42PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 25, 2017 at 09:50:31AM -0700, Guenter Roeck wrote:
> > Hi Greg,
> >
> > would you be open to accepting the tcpm [1] and tcpci [2] drivers into
> > drivers/staging for v4.12 ?
>
> What's the rush?
>
It has been a long time, and it avoids duplicate work and submissions,
including for drivers depending on it, such as the fusb302 driver submitted
by Hans de Goede [1] for which we have a (not yet published) driver based on
tcpm as well. If for nothing else, it widens the audience.
> > The drivers are not ready for prime time, yet there is interest by others
> > to have them available and to help improving the code. I could create a
> > repository/branch at github to enable that, but drivers/staging seems to be
> > a better approach.
>
> Sure, if you want to maintain it in the kernel, and send me patches that
> way for changes, I'll be glad to take them into staging, just send me a
> patch that adds them to the tree and I'll merge them for 4.12-rc1.
>
Ok, will do.
Thanks,
Guenter
---
[1] https://lkml.org/lkml/2017/4/21/312
next prev parent reply other threads:[~2017-04-25 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:50 typec: tcpm/tcpci drivers acceptable for drivers/staging in v4.12 ? Guenter Roeck
2017-04-25 17:37 ` Greg Kroah-Hartman
2017-04-25 17:54 ` Guenter Roeck [this message]
2017-04-25 18:02 ` Greg Kroah-Hartman
2017-04-25 18:25 ` Guenter Roeck
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=20170425175402.GA28665@roeck-us.net \
--to=linux@roeck-us.net \
--cc=badhri@google.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mats.dev.list@gmail.com \
--cc=oneukum@suse.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