From: Greg KH <gregkh@linuxfoundation.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: drivers to avoid?
Date: Thu, 16 Feb 2017 13:54:40 -0800 [thread overview]
Message-ID: <20170216215440.GA10588@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702162139150.2121@hadrien>
On Thu, Feb 16, 2017 at 09:40:10PM +0100, Julia Lawall wrote:
> Greg,
>
> Are there any staging drivers to avoid at this time?
Nope, all should be good. During the merge window (the next 2 weeks) I
will queue things up in the staging-testing branch, so people should use
that, but note that it will be rebased at times, so things will get
tricky until 4.11-rc1 is out.
If anyone has any specific questions about this, please let me know.
thanks,
greg k-h
prev parent reply other threads:[~2017-02-16 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 20:40 drivers to avoid? Julia Lawall
2017-02-16 21:54 ` Greg KH [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=20170216215440.GA10588@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=outreachy-kernel@googlegroups.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 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.