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-01
Date: Thu, 03 Aug 2017 12:16:35 +0300 [thread overview]
Message-ID: <87fud9ovt8.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1501582910.2588.45.camel@coelho.fi> (Luca Coelho's message of "Tue, 01 Aug 2017 13:21:50 +0300")
Luca Coelho <luca@coelho.fi> writes:
> Hi Kalle,
>
> Here's my first pull-request intended for v4.14.=C2=A0 It contain=C2=A0ge=
neric
> development work, with improvements, bug fixes and
> cleanup all around.=C2=A0 More=C2=A0details in the tag description.
>
> As I mentioned earlier today, I left Emmanuel's "iwlwifi: mvm: fix TCP
> CSUM offload with WEP and A000 series" patch out of this pull-req,
> because I'll include it in the one for 4.13.
>
> 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 d28ac7be15c70343cb270648e252f54d770eca=
6a:
>
> rtlwifi: rtl8821ae: Fix HW_VAR_NAV_UPPER operation (2017-07-28 18:42:59=
+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-01
>
> for you to fetch changes up to d20e30af7e65811955af5bc2a268ae75cd14e99e:
>
> iwlwifi: mvm: don't retake the pointer to skb's CB (2017-08-01 12:41:46=
+0300)
>
> ----------------------------------------------------------------
> First batch of iwlwifi patches for 4.14
>
> * Reorganization of the code into separate directories continues;
> * A couple of new minor features;
> * Fixes and cleanups here and there.
>
> ----------------------------------------------------------------
Pulled, thanks.
--=20
Kalle Valo
prev parent reply other threads:[~2017-08-03 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 10:21 pull-request: iwlwifi-next 2017-08-01 Luca Coelho
2017-08-03 9:16 ` 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=87fud9ovt8.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).