From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-next 2017-06-06
Date: Mon, 12 Jun 2017 19:38:06 +0300 [thread overview]
Message-ID: <87d1a988lt.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1496777308.9478.107.camel@coelho.fi> (Luca Coelho's message of "Tue, 06 Jun 2017 22:28:28 +0300")
Luca Coelho <luca@coelho.fi> writes:
> Here's my first pull-request intended for v4.13.=C2=A0 This one is double=
the
> size of my normal pull-request since I'm sending to batches at once. It
> contain=C2=A0generic development work, with improvements, bug fixes and
> cleanup all around.=C2=A0 More=C2=A0details in the tag description.
>
> I have sent this out before, and kbuildbot reported success.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 219569ad0c41df7a7f999a2cad688c6b6ce173=
e2:
>
> rsi: use subdirectory for firmware file (2017-06-01 12:51:19 +0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git =
tags/iwlwifi-next-for-kalle-2017-06-06
>
> for you to fetch changes up to 0ae0bb3f409d48251a9a1730a514b3521d8f6042:
>
> iwlwifi: remove unnecessary code in iwl_trans_alloc_tx_cmd (2017-06-05 =
23:34:31 +0300)
>
> ----------------------------------------------------------------
> First batch of iwlwifi driver patches 4.13
>
> * Loads of FW API documentation improvements (for tools and htmldoc);
> * Continued work for the new A000 family;
> * Bumped the maximum supported FW API to 31;
> * Improve the differentiation between 8000, 9000 and A000 families;
> * A lot of fixes and cleanups here and there;
>
> ----------------------------------------------------------------
Pulled, thanks.
Because an hour earlier I had fast forwarded to latest net-next there
were two conflicts. This is what I wrote to the commit log, please
double check:
kvalo: There were conflicts iwl_mvm_stop_device() and
iwl_mvm_tcool_set_cur_state(). The former was easy but latter needed more
thought. Apparently the mutex was taken too late, so I fixed so that the mu=
tex
is taken first and then check for iwl_mvm_firmware_running().
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next=
.git/commit/?id=3D833689044e13a3fb8c6c03ad868375670d97010b
--=20
Kalle Valo
prev parent reply other threads:[~2017-06-12 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 19:28 pull-request: iwlwifi-next 2017-06-06 Luca Coelho
2017-06-12 16:38 ` 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=87d1a988lt.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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).