From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [PATCH v7 2/2] wireless: integrate wil6210 driver into build structure
Date: Wed, 14 Nov 2012 10:30:55 +0100 [thread overview]
Message-ID: <1352885455.9510.16.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <4396194.ZVOZT6GsHI@lx-vladimir>
On Wed, 2012-11-14 at 11:22 +0200, Vladimir Kondratiev wrote:
> OK, I will. Meanwhile, I'll also provide reason here:
[...]
> Does this explains the change? I'll add this exact text to the commit
> message.
Yeah I did actually understand the change, I was just asking that you
add the explanation to the commit log :)
Thanks!
johannes
prev parent reply other threads:[~2012-11-14 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 12:23 [PATCH v7 0/2] driver for 60g Wilocity chip wil6210 Vladimir Kondratiev
2012-11-13 12:23 ` [PATCH v7 1/2] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-11-13 13:06 ` Joe Perches
2012-11-13 21:44 ` Andrew Morton
2012-11-13 22:39 ` Joe Perches
2012-11-13 22:52 ` Andrew Morton
2012-11-14 12:21 ` Vladimir Kondratiev
2012-11-13 19:54 ` Johannes Berg
[not found] ` <16914852.FhZEtcXc7Y@lx-vladimir>
2012-11-16 13:40 ` Johannes Berg
2012-11-18 16:35 ` Vladimir Kondratiev
2012-11-13 12:23 ` [PATCH v7 2/2] wireless: integrate wil6210 driver into build structure Vladimir Kondratiev
2012-11-13 19:54 ` Johannes Berg
2012-11-13 23:23 ` Julian Calaby
[not found] ` <4652801.Xt8tN7pgs4@lx-vladimir>
2012-11-14 9:32 ` Johannes Berg
2012-11-14 13:48 ` Vladimir Kondratiev
[not found] ` <4396194.ZVOZT6GsHI@lx-vladimir>
2012-11-14 9:30 ` Johannes Berg [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=1352885455.9510.16.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.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.