From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] ath10k: search DT for qcom,ath10k-calibration-variant
Date: Thu, 09 Mar 2017 16:49:34 +0100 [thread overview]
Message-ID: <1998122.7sAEb6onT0@bentobox> (raw)
In-Reply-To: <20170309152416.4090-1-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Donnerstag, 9. März 2017 16:36:15 CET Sven Eckelmann wrote:
> .../bindings/net/wireless/qcom,ath10k.txt | 3 +++
> drivers/net/wireless/ath/ath10k/core.c | 31 +++++++++++++++++++++-
> 2 files changed, 33 insertions(+), 1 deletion(-)
Nice, not only used the wrong account - also used the wrong patch file. Let me
try that again :)
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-09 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 15:24 [RFC] ath10k: search DT for qcom,ath10k-calibration-variant Sven Eckelmann
2017-03-09 15:49 ` Sven Eckelmann [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=1998122.7sAEb6onT0@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@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).