From: Kalle Valo <kvalo@codeaurora.org>
To: "Grumbach\, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "luca\@coelho.fi" <luca@coelho.fi>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>, "Coelho\,
Luciano" <luciano.coelho@intel.com>
Subject: Re: [PATCH 0/5] iwlwifi: updates intended for v4.16 2017-12-23
Date: Sun, 14 Jan 2018 12:26:35 +0200 [thread overview]
Message-ID: <87y3l07n38.fsf@codeaurora.org> (raw)
In-Reply-To: <1515914548.7436.1.camel@intel.com> (Emmanuel Grumbach's message of "Sun, 14 Jan 2018 07:22:28 +0000")
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com> writes:
> On Fri, 2018-01-12 at 13:31 +0200, Kalle Valo wrote:
>> From: Luca Coelho <luciano.coelho@intel.com>
>>
>> > Luca Coelho (1):
>> > iwlwifi: mvm: check if mac80211_queue is valid in
>> > iwl_mvm_disable_txq
>> >
>> > Mordechay Goodstein (1):
>> > iwlwifi: set default timstamp marker cmd
>> >
>> > Sara Sharon (3):
>> > iwlwifi: mvm: flip AMSDU addresses only for 9000 family
>> > iwlwifi: mvm: take RCU lock before dereferencing
>> > iwlwifi: mvm: move TSO segment to a separate function
>>
>> Most likely the merge window starts in 9 days so I need to start
>> getting patches ready. As Luca is away should I apply these patches
>> directly to wireless-drivers-next?
>>
>
> First let me thank you for tracking this. I don't see anything that we
> really need in 4.16 here. Besides Luca's UBSAN warning, all the rest
> is for a new device family which won't be supported in 4.16 anyway.
>
> So I opt to wait for Luca here.
Ok, I'll wait for him then.
--
Kalle Valo
next prev parent reply other threads:[~2018-01-14 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 9:21 [PATCH 0/5] iwlwifi: updates intended for v4.16 2017-12-23 Luca Coelho
2017-12-23 9:21 ` [PATCH 1/5] iwlwifi: mvm: flip AMSDU addresses only for 9000 family Luca Coelho
2017-12-23 9:21 ` [PATCH 2/5] iwlwifi: mvm: take RCU lock before dereferencing Luca Coelho
2017-12-23 9:21 ` [PATCH 3/5] iwlwifi: mvm: move TSO segment to a separate function Luca Coelho
2017-12-23 9:21 ` [PATCH 4/5] iwlwifi: set default timstamp marker cmd Luca Coelho
2017-12-23 9:22 ` [PATCH 5/5] iwlwifi: mvm: check if mac80211_queue is valid in iwl_mvm_disable_txq Luca Coelho
2018-01-12 11:31 ` [PATCH 0/5] iwlwifi: updates intended for v4.16 2017-12-23 Kalle Valo
2018-01-14 7:22 ` Grumbach, Emmanuel
2018-01-14 10:26 ` Kalle Valo [this message]
2018-02-03 6:51 ` Luca 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=87y3l07n38.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--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.