From: David Miller <davem@davemloft.net>
To: keescook@chromium.org
Cc: chunkeey@googlemail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, gregkh@linuxfoundation.org,
linville@tuxdriver.com, kvalo@qca.qualcomm.com
Subject: Re: [PATCH 16/20] drivers/net/wireless/p54: remove depends on CONFIG_EXPERIMENTAL
Date: Tue, 22 Jan 2013 14:12:52 -0500 (EST) [thread overview]
Message-ID: <20130122.141252.781223481145097577.davem@davemloft.net> (raw)
In-Reply-To: <CAGXu5jJCQshUntUk7MeZds59B2fa54GnonOz28dM1x2spEEGDg@mail.gmail.com>
From: Kees Cook <keescook@chromium.org>
Date: Tue, 22 Jan 2013 10:40:12 -0800
> On Tue, Jan 22, 2013 at 10:37 AM, Christian Lamparter
> <chunkeey@googlemail.com> wrote:
>> Aren't these patches going through wireless-next
>> or linux-next?
>
> They can go however it makes things easiest. Greg has offered to carry
> them in driver-core if Dave doesn't want to carry them in netdev.
Greg can take these:
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2013-01-22 19:12 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 [this message]
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 ` [PATCH 0/20] net: remove CONFIG_EXPERIMENTAL Greg Kroah-Hartman
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=20130122.141252.781223481145097577.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chunkeey@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).