From: Kalle Valo <kvalo@codeaurora.org>
To: Luciano Coelho <luciano.coelho@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/16] iwlwifi: updates intended for v4.19 2018-07-27
Date: Wed, 01 Aug 2018 11:17:12 +0300 [thread overview]
Message-ID: <87muu68prr.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <a3d8f0dcd43467c412ffcb72e2b4361f210a1cc6.camel@intel.com> (Luciano Coelho's message of "Wed, 01 Aug 2018 11:11:25 +0300")
Luciano Coelho <luciano.coelho@intel.com> writes:
> On Wed, 2018-08-01 at 10:56 +0300, Kalle Valo wrote:
>> Luca Coelho <luca@coelho.fi> writes:
>>
>> > From: Luca Coelho <luciano.coelho@intel.com>
>> >
>> > Hi,
>> >
>> > Here's one more set of patches intended for v4.19. It contains
>> > some
>> > bugfixes, cleanups and more work on supporting the 22560 family of
>> > devices.
>> >
>> > The changes are:
>> >
>> > * New PCI IDs for 22000 and 22560;
>> > * Some fixes and an improvement in debug dumps and recording;
>> > * Remove some old dead code;
>> > * Fix compilation when only IPv6 is not enabled;
>>
>> -EPARSE, "when only ... not"?
>
> That's perfectly fine grammar. :) "If only IPv6 is not enabled,
> compilation fails. Fix that."
>
> Though not exactly what I meant, I meant "when IPv6 is not enabled".
Yeah, that's more understandable :)
Also I got last three patches two times, but maybe that was a problem
with email servers or something.
--
Kalle Valo
next prev parent reply other threads:[~2018-08-01 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 12:48 [PATCH 00/16] iwlwifi: updates intended for v4.19 2018-07-27 Luca Coelho
2018-07-27 12:48 ` [PATCH 01/16] iwlwifi: pcie: add a bunch of PCI IDs for 22000 and 22560 Luca Coelho
2018-07-27 12:48 ` [PATCH 02/16] iwlwifi: pcie: support rx structures for 22560 devices Luca Coelho
2018-07-27 12:48 ` [PATCH 03/16] iwlwifi: support new rx_mpdu_desc api Luca Coelho
2018-07-27 12:48 ` [PATCH 04/16] iwlwifi: pcie: unionize used bd and completion descriptor Luca Coelho
2018-07-27 12:48 ` [PATCH 05/16] iwlwifi: pcie: move rxb retrieval to a helper function Luca Coelho
2018-07-27 12:48 ` [PATCH 06/16] iwlwifi: trans: add a new op for getting DMA data Luca Coelho
2018-07-27 12:48 ` [PATCH 07/16] iwlwifi: allow masking out memory areas from the fw dump Luca Coelho
2018-07-27 12:48 ` [PATCH 08/16] iwlwifi: d3: disable dbg recording before entering D3 Luca Coelho
2018-07-27 12:48 ` [PATCH 09/16] iwlwifi: mvm: configure multi RX queue Luca Coelho
2018-07-27 12:48 ` [PATCH 10/16] iwlwifi: pcie: don't access periphery registers when not available Luca Coelho
2018-07-27 12:48 ` [PATCH 11/16] Revert "iwlwifi: implement fseq version mismatch warning" Luca Coelho
2018-07-27 12:48 ` [PATCH 12/16] iwlwifi: hard code power save mode to CAM for 22560 devices Luca Coelho
2018-07-27 12:48 ` [PATCH 13/16] iwlwifi: mvm: remove dead gscan code Luca Coelho
2018-07-27 13:05 ` [PATCH 14/16] iwlwifi: pcie: include tcp.h implicitly Luca Coelho
2018-07-27 13:05 ` [PATCH 15/16] iwlwifi: move some msix and rx functions to a common place Luca Coelho
2018-07-27 13:06 ` [PATCH 16/16] iwlwifi: pcie: split tx to amsdu and non amsdu Luca Coelho
2018-08-01 7:56 ` [PATCH 00/16] iwlwifi: updates intended for v4.19 2018-07-27 Kalle Valo
2018-08-01 8:11 ` Luciano Coelho
2018-08-01 8:17 ` Kalle Valo [this message]
2018-08-01 8:19 ` Luciano Coelho
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=87muu68prr.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
/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.