> > On Tue, Nov 11, 2014 at 02:55:33AM +0200, Emmanuel Grumbach wrote: > > From: Emmanuel Grumbach <emmanuel.grumbach@xxxxxxxxx> > > > > commit 9180ac50716a097a407c6d7e7e4589754a922260 upstream. > > > > The LTR is the handshake between the device and the root complex about > > the latency allowed when the bus exits power save. This configuration > > was missing and this led to high latency in the link power up. The end > > user could experience high latency in the network because of this. > > > > Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@xxxxxxxxx> > > --- > > drivers/net/wireless/iwlwifi/iwl-trans.h | 2 ++ > > drivers/net/wireless/iwlwifi/mvm/fw-api-power.h | 35 > ++++++++++++++++++++++++- > > drivers/net/wireless/iwlwifi/mvm/fw-api.h | 1 + > > drivers/net/wireless/iwlwifi/mvm/fw.c | 9 +++++++ > > drivers/net/wireless/iwlwifi/mvm/ops.c | 1 + > > drivers/net/wireless/iwlwifi/pcie/trans.c | 16 ++++++----- > > 6 files changed, 56 insertions(+), 8 deletions(-) > > This doesn't apply to the 3.14-stable tree: > > checking file drivers/net/wireless/iwlwifi/iwl-trans.h > Hunk #1 succeeded at 514 (offset 25 lines). > Hunk #2 succeeded at 540 (offset 26 lines). > checking file drivers/net/wireless/iwlwifi/mvm/fw-api-power.h > Hunk #1 succeeded at 72 with fuzz 1 (offset 5 lines). > checking file drivers/net/wireless/iwlwifi/mvm/fw-api.h > Hunk #1 FAILED at 138. > 1 out of 1 hunk FAILED > checking file drivers/net/wireless/iwlwifi/mvm/fw.c > Hunk #1 succeeded at 443 with fuzz 2. > checking file drivers/net/wireless/iwlwifi/mvm/ops.c > Hunk #1 FAILED at 293. > 1 out of 1 hunk FAILED > checking file drivers/net/wireless/iwlwifi/pcie/trans.c > Hunk #1 succeeded at 89 (offset -27 lines). > Hunk #2 succeeded at 106 (offset -27 lines). > > > :( I guess patches were sent / applied in different order. I'll check it out. It'll take time though. I am currently travelling. Thanks for the heads up. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html