From: Kalle Valo <kvalo@qca.qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: <linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: pull-request: wireless-drivers-next 2015-01-22
Date: Thu, 22 Jan 2015 14:31:53 +0200 [thread overview]
Message-ID: <8761bznghy.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87h9vjnic4.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Thu, 22 Jan 2015 13:52:11 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Hi Dave,
>
> now a bigger pull request for net-next. Rafal found a UTF-8 bug in
> patchwork[1] and because of that two commits (d0c102f70aec and
> d0f66df5392a) have his name corrupted:
>
> Acked-by: Rafa? Mi?ecki <zajec5@gmail.com>
>
> Somehow I failed to spot that when I commited the patches. As rebasing
> public git trees is bad, I thought we can live with these and decided
> not to rebase. But I'll pay close attention to this in the future to
> make sure that it won't happen again. Also we requested an update to
> patchwork.kernel.org, the latest patchwork doesn't seem to have this
> bug.
>
> Also please note this pull request also adds one DT binding doc, but
> this was reviewed in the device tree list:
>
> .../bindings/net/wireless/qcom,ath10k.txt | 30 +
>
> Please let me know if you have any issues.
I almost missed that there's actually a small conflict with net-next:
CONFLICT (content): Merge conflict in drivers/net/wireless/ath/wil6210/cfg80211.c
Please fix it like this in wil_cid_fill_sinfo():
if (test_bit(wil_status_fwconnected, wil->status)) {
sinfo->filled |= BIT(NL80211_STA_INFO_SIGNAL);
sinfo->signal = reply.evt.sqi;
}
--
Kalle Valo
next prev parent reply other threads:[~2015-01-22 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:52 pull-request: wireless-drivers-next 2015-01-22 Kalle Valo
2015-01-22 12:31 ` Kalle Valo [this message]
[not found] ` <87h9vjnic4.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2015-01-27 0:12 ` David Miller
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=8761bznghy.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).