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-08-11
Date: Fri, 11 Aug 2017 17:09:30 +0300 [thread overview]
Message-ID: <87efsidwmd.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1502435046.15969.207.camel@coelho.fi> (Luca Coelho's message of "Fri, 11 Aug 2017 10:04:06 +0300")
Luca Coelho <luca@coelho.fi> writes:
> Here's my second pull-request intended for v4.14.=C2=A0 It contains
> more=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 2db3aaba0a9fc769435477059c1224c4390617=
52:
>
> rt2x00: Fix MMIC Countermeasures (2017-08-08 14:53:36 +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-08-11
>
> for you to fetch changes up to 88c5f476bac964eb96e751b004f5684c90629eab:
>
> iwlwifi: mvm: fix the coex firmware API (2017-08-09 21:14:44 +0300)
>
> ----------------------------------------------------------------
> Sencond batch of iwlwifi patches for 4.14
>
> * Some more code moved to a new directory;
> * Fixes in LED handling;
> * Some FW API updates;
> * General fixes and cleanups here and there.
>
> ----------------------------------------------------------------
Pulled, thanks.
--=20
Kalle Valo
prev parent reply other threads:[~2017-08-11 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 7:04 pull-request: iwlwifi-next 2017-08-11 Luca Coelho
2017-08-11 14:09 ` 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=87efsidwmd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.