From: Johannes Berg <johannes@sipsolutions.net>
To: Mahesh Palivela <maheshp@posedge.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: VHT (11ac) Association
Date: Tue, 24 Jul 2012 16:10:49 +0200 [thread overview]
Message-ID: <1343139049.4415.28.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <952C5D5D0470AE4FB7D8A75C6ADC71CA0FCC6FCB@mbx022-e1-nj-10.exch022.domain.local>
On Tue, 2012-07-24 at 03:33 +0000, Mahesh Palivela wrote:
> VHT (11ac) Association related change version 2. Incorporated Johannes review comments.
>
> Signed-off-by: Mahesh Palivela <maheshp@posedge.com>
> Reviewed-by: Johannes Berg <johannes@sipsolutions.net>
Applied, but I fixed up the commit message. Please review & make a
better one next time :)
johannes
next prev parent reply other threads:[~2012-07-24 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 3:33 [PATCH v2] mac80211: VHT (11ac) Association Mahesh Palivela
2012-07-24 3:37 ` Julian Calaby
2012-07-24 3:44 ` Mahesh Palivela
2012-07-24 14:10 ` Johannes Berg [this message]
2012-07-24 14:32 ` Mahesh Palivela
2012-07-24 14:34 ` 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=1343139049.4415.28.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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.