From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-next 2013-10-07
Date: Wed, 30 Oct 2013 18:43:50 +0100 [thread overview]
Message-ID: <1383155030.13488.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <527143AA.5070900@gmail.com> (sfid-20131030_183651_825331_C6DEAE75)
And yes, I support that - Emmanuel is taking over the tree from me :-)
johannes
next prev parent reply other threads:[~2013-10-30 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 17:36 pull-request: iwlwifi-next 2013-10-07 Emmanuel Grumbach
2013-10-30 17:43 ` Johannes Berg [this message]
2013-10-30 20:31 ` [PATCH 1/9] iwlwifi: mvm: update UAPSD support TLV bits Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 2/9] iwlwifi: transport config n_no_reclaim_cmds should be unsigned Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 3/9] iwlwifi: mvm: BT Coex fix NULL pointer dereference Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 4/9] iwlwifi: pcie: move warning message into warning Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 5/9] iwlwifi: mvm: capture the FCS in monitor mode Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 6/9] iwlwifi: mvm: add missing break in debugfs Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 7/9] iwlwifi: warn if firmware image doesn't exist Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 8/9] iwlwifi: remove duplicate includes Emmanuel Grumbach
2013-10-30 20:31 ` [PATCH 9/9] iwlwifi: mvm: BT Coex - fix copy paste issue Emmanuel Grumbach
2013-11-05 20:53 ` pull-request: iwlwifi-next 2013-10-07 John W. Linville
2013-11-05 20:57 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2013-10-07 9:56 Johannes Berg
2013-10-08 10:59 ` Johannes Berg
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=1383155030.13488.11.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.