Linux wireless drivers development
 help / color / mirror / Atom feed
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-01-26
Date: Fri, 27 Jan 2017 13:24:19 +0200	[thread overview]
Message-ID: <87lgtw7nks.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1485462650.26003.11.camel@coelho.fi> (Luca Coelho's message of "Thu, 26 Jan 2017 22:30:50 +0200")

Luca Coelho <luca@coelho.fi> writes:

> Hi Kalle,
>
> Here's my first pull-request intended for v4.11.  It has a bunch of
> fixes, cleanups and improvements here and there, as well as a few new
> features.  More details in the tag description.
>
> I have sent this out before and kbuildbot didn't find any issues.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 106e0deca1ac6ac627a10617fe77a95200cb01a7:
>
>   rtlwifi: rtl8192cu: Convert driver to use common macros (2017-01-20 12:06:10 +0200)
>
> 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-01-26
>
> for you to fetch changes up to 758c98e089389e90732fe45087fdee3177493a81:
>
>   iwlwifi: mvm: cleanup redundant assignment (2017-01-26 09:39:02 +0200)
>
> ----------------------------------------------------------------
> Some improvements, bugfixes and new features:
>  * A bunch of cleanups here and there;
>  * A few simple bugfixes;
>  * Some more work in preparation for A000 family support;
>  * Add support for radiotap timestamps;
>  * Some work on our firmware debugging capabilities;
>
> ----------------------------------------------------------------

Pulled, thanks.

-- 
Kalle Valo

      reply	other threads:[~2017-01-27 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 20:30 pull-request: iwlwifi-next 2017-01-26 Luca Coelho
2017-01-27 11:24 ` 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=87lgtw7nks.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