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@intel.com,
	david.e.box@intel.com, joe.konno@intel.com
Subject: Re: pull-request: iwlwifi-next 2019-04-18-2
Date: Thu, 25 Apr 2019 18:29:18 +0300	[thread overview]
Message-ID: <87ef5qw1bl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <560ba2b6a20ac9842fd6a5a5d786def1077811f4.camel@coelho.fi> (Luca Coelho's message of "Fri, 19 Apr 2019 10:37:18 +0300")

Luca Coelho <luca@coelho.fi> writes:

> This is a new version of my pull request on top of your tree after you
> fast-forwarded to net-next, to avoid a small conflict.
>
> This is the third batch of patches intended for v5.2.  This includes
> the last patchset I sent.  Usual development work.  More details about
> the contents 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 5c2e6e14a0ad24a35d9d2b318204c8c012d9d618:
>
>   Merge branch 'net-add-reset-controller-driven-PHY-reset' (2019-04-18 17:43:11 -0700)
>
> 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-2019-04-18-2
>
> for you to fetch changes up to 69166f7a37dc0bde5a3c26945e3cdbfc740b0562:
>
>   iwlwifi: dbg_ini: set dump bit only when trigger collection is certain (2019-04-19 10:27:34 +0300)
>
> ----------------------------------------------------------------
> Third batch of patches intended for v5.2
>
> * Bump the 20000-series FW API version supported;
> * Work on the new debugging infra continues;
> * One clean-up to prevent a bogus warning with clang;
> * A small cleanup in the PCI ID list;
> * Work on new hardware continues;
> * RTT confidence indication support for FTM;
> * An improvement in HE rate-scaling;
>
> ----------------------------------------------------------------

Pulled, thanks Luca.

-- 
Kalle Valo

      reply	other threads:[~2019-04-25 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 12:58 pull-request: iwlwifi-next 2019-04-18 Luca Coelho
2019-04-19  7:37 ` pull-request: iwlwifi-next 2019-04-18-2 Luca Coelho
2019-04-25 15:29   ` 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=87ef5qw1bl.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=david.e.box@intel.com \
    --cc=joe.konno@intel.com \
    --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