From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, linuxwifi <linuxwifi@intel.com>
Subject: Re: pull-request: iwlwifi-next 2017-04-26
Date: Wed, 26 Apr 2017 14:23:09 +0300 [thread overview]
Message-ID: <87mvb3xvj6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1493195190.14233.2.camel@coelho.fi> (Luca Coelho's message of "Wed, 26 Apr 2017 11:26:30 +0300")
Luca Coelho <luca@coelho.fi> writes:
> Here's another pull-request intended for v4.12.=C2=A0 This is generic
> development work, nothing really stands out.=C2=A0 More=C2=A0details in t=
he 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 a0597834dc0e1af68f48f92b31617b360a14df=
c8:
>
> rt2800: fix mt7620 E2 channel registers (2017-04-20 14:00:54 +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-04-26
>
> for you to fetch changes up to 291084951825e1efca081926b10bf3ff7e872476:
>
> iwlwifi: adjust NVM parsing APIs for new a000 method (2017-04-25 23:08:=
32 +0300)
>
> ----------------------------------------------------------------
> One more pull-request intended for 4.12. These are the changes:
>
> * The firmware for 7265D and 3168 NICs is frozen at version 29;
> * Sari continues working heavily on support for A000 series;
> * A bunch of fixes;
> * Some cleanups here and there;
>
> ----------------------------------------------------------------
Pulled, thanks.
--=20
Kalle Valo
prev parent reply other threads:[~2017-04-26 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 8:26 pull-request: iwlwifi-next 2017-04-26 Luca Coelho
2017-04-26 11:23 ` 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=87mvb3xvj6.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--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).