From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: fix board data fetch error message
Date: Mon, 30 Nov 2015 17:05:40 +0200 [thread overview]
Message-ID: <8737vnjznf.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1448040794-1139-1-git-send-email-poh@qca.qualcomm.com> (Peter Oh's message of "Fri, 20 Nov 2015 09:33:14 -0800")
Peter Oh <poh@qca.qualcomm.com> writes:
> The error message order of board data fetch is board info,
> directory, and then file name, hence place print arguments
> in the order.
>
> Fixes: 0a51b343abfe ("ath10k: add board 2 API support")
> Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
Applied, thanks.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-11-30 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 17:33 [PATCH] ath10k: fix board data fetch error message Peter Oh
2015-11-30 15:05 ` Kalle Valo [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=8737vnjznf.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox