From: Kalle Valo <kvalo@codeaurora.org>
To: Wei-Ning Huang <wnhuang@chromium.org>
Cc: Linux-Wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Wei-Ning Huang <wnhuang@chromium.org>
Subject: Re: mwifiex: fixup error messages
Date: Wed, 11 May 2016 19:01:25 +0000 (UTC) [thread overview]
Message-ID: <20160511190125.982DC61324@smtp.codeaurora.org> (raw)
In-Reply-To: <1462861283-11103-1-git-send-email-wnhuang@chromium.org>
Wei-Ning Huang <wnhuang@chromium.org> wrote:
> Use dev_err instead of pr_err and add newline character at the end.
>
> Signed-off-by: Wei-Ning Huang <wnhuang@chromium.org>
Thanks, 1 patch applied to wireless-drivers-next.git:
50d4d8feb913 mwifiex: fixup error messages
--
Sent by pwcli
https://patchwork.kernel.org/patch/9054541/
prev parent reply other threads:[~2016-05-11 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 6:21 [PATCH] mwifiex: fixup error messages Wei-Ning Huang
2016-05-11 19:01 ` 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=20160511190125.982DC61324@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wnhuang@chromium.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).