From: Kalle Valo <kvalo@codeaurora.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k_htc: wmi: match wait_for_completion_timeout return type
Date: Thu, 14 May 2015 20:05:37 +0300 [thread overview]
Message-ID: <87fv6zccny.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1431621821-8173-1-git-send-email-hofrat@osadl.org> (Nicholas Mc Guire's message of "Thu, 14 May 2015 18:43:41 +0200")
Nicholas Mc Guire <hofrat@osadl.org> writes:
> Patch is against 4.1-rc3 (localversion-next is -next-20150514)
BTW, this info should be under "---" line so that it doesn't get stored
to the actual commit log.
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: QCA ath9k Development <ath9k-devel@qca.qualcomm.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath9k_htc: wmi: match wait_for_completion_timeout return type
Date: Thu, 14 May 2015 20:05:37 +0300 [thread overview]
Message-ID: <87fv6zccny.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1431621821-8173-1-git-send-email-hofrat@osadl.org> (Nicholas Mc Guire's message of "Thu, 14 May 2015 18:43:41 +0200")
Nicholas Mc Guire <hofrat@osadl.org> writes:
> Patch is against 4.1-rc3 (localversion-next is -next-20150514)
BTW, this info should be under "---" line so that it doesn't get stored
to the actual commit log.
--
Kalle Valo
next prev parent reply other threads:[~2015-05-14 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 16:43 [PATCH] ath9k_htc: wmi: match wait_for_completion_timeout return type Nicholas Mc Guire
2015-05-14 17:05 ` Kalle Valo [this message]
2015-05-14 17:05 ` Kalle Valo
2015-05-14 17:40 ` Nicholas Mc Guire
2015-05-21 13:59 ` [ath9k-devel] " Kalle Valo
2015-05-21 13:59 ` Kalle Valo
2015-08-13 12:26 ` [ath9k-devel] " Kalle Valo
2015-08-13 12:26 ` Kalle Valo
2015-08-13 12:26 ` Kalle Valo
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=87fv6zccny.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@lists.ath9k.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.