From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/20] net: remove CONFIG_EXPERIMENTAL
Date: Tue, 22 Jan 2013 12:34:41 -0800 [thread overview]
Message-ID: <20130122203441.GA2580@kroah.com> (raw)
In-Reply-To: <1358879444-25834-1-git-send-email-keescook@chromium.org>
On Tue, Jan 22, 2013 at 10:30:24AM -0800, Kees Cook wrote:
> Here's what's left of the "remove experimental"[1] tree, all for netdev.
>
> What would be the preference for taking these patches for linux-next?
> Should they go via the netdev tree, or should I ask Greg KH to take them
> via driver-core?
All now applied, thanks.
greg k-h
prev parent reply other threads:[~2013-01-22 20:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 18:30 [PATCH 0/20] net: remove CONFIG_EXPERIMENTAL Kees Cook
2013-01-22 18:30 ` [PATCH 01/20] drivers/net/ethernet/fujitsu: remove depends on CONFIG_EXPERIMENTAL Kees Cook
2013-01-22 18:30 ` [PATCH 02/20] drivers/net/ethernet/icplus: " Kees Cook
2013-01-22 18:30 ` [PATCH 03/20] drivers/net/ethernet/microchip: " Kees Cook
2013-01-22 18:30 ` [PATCH 04/20] drivers/net/ethernet/racal: " Kees Cook
2013-01-22 18:30 ` [PATCH 05/20] drivers/net/ethernet/seeq: " Kees Cook
2013-01-22 18:30 ` [PATCH 06/20] drivers/net/ethernet/stmicro/stmmac: " Kees Cook
2013-01-22 18:30 ` [PATCH 07/20] drivers/net/ethernet/sun: " Kees Cook
2013-01-22 18:30 ` [PATCH 08/20] drivers/net/hippi: " Kees Cook
2013-01-22 18:30 ` [PATCH 09/20] drivers/net/irda: " Kees Cook
2013-01-22 18:30 ` [PATCH 10/20] drivers/net/ppp: " Kees Cook
2013-01-22 18:30 ` [PATCH 11/20] drivers/net/wireless: " Kees Cook
2013-01-22 18:30 ` [PATCH 12/20] drivers/net/wireless/ath/ath6kl: " Kees Cook
2013-01-22 18:36 ` Kalle Valo
2013-01-22 18:30 ` [PATCH 13/20] drivers/net/wireless/ath/carl9170: " Kees Cook
2013-01-22 18:30 ` [PATCH 14/20] drivers/net/wireless/b43: " Kees Cook
2013-01-22 18:30 ` [PATCH 15/20] drivers/net/wireless/ipw2x00: " Kees Cook
2013-01-22 18:30 ` [PATCH 16/20] drivers/net/wireless/p54: " Kees Cook
2013-01-22 18:37 ` Christian Lamparter
2013-01-22 18:40 ` Kees Cook
2013-01-22 19:12 ` David Miller
2013-01-22 19:14 ` John W. Linville
2013-01-22 19:59 ` Greg KH
2013-01-22 18:30 ` [PATCH 17/20] drivers/net/wireless/rt2x00: " Kees Cook
2013-01-22 18:30 ` [PATCH 18/20] drivers/net/wireless/rtl818x: " Kees Cook
2013-01-22 18:30 ` [PATCH 19/20] drivers/net/wireless/zd1211rw: " Kees Cook
2013-01-22 18:30 ` [PATCH 20/20] drivers/net/wireless/rtlwifi: " Kees Cook
2013-01-22 20:34 ` Greg Kroah-Hartman [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=20130122203441.GA2580@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.