linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: kvalo@codeaurora.org, jikos@kernel.org,
	linux-kernel@vger.kernel.org, ath10k@lists.infradead.org,
	linux-wireless@vger.kernel.org
Subject: Re: ath10k regression on XPS13
Date: Tue, 21 Feb 2017 16:01:03 -0500 (EST)	[thread overview]
Message-ID: <20170221.160103.272609294929297575.davem@davemloft.net> (raw)
In-Reply-To: <CA+55aFyqH3WAKsD_AaCe905zJbPzTXGygu2eiD1L0d6c2sAkGA@mail.gmail.com>

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue, 21 Feb 2017 10:52:33 -0800

> On Tue, Feb 21, 2017 at 10:18 AM, David Miller <davem@davemloft.net> wrote:
>>
>> Kalle I really wanted to send my net-next pull request to Linus later
>> today.  But I guess I have to wait for this ath10k first.
> 
> Feel free to send it to me - it sounds like the regression is
>  (a) easy to work around
> and
>  (b) has a fix coming up.
> 
> And it won't even be something that I personally notice, since I have
> the prev-gen XPS13 that has intel wireless.

I have the revert in my tree, it's all good.

I'll let my tree sit quietly for a few hours then send a pull
request out later tonight.

      reply	other threads:[~2017-02-21 21:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 15:20 [GIT PULL] HID for 4.11 Jiri Kosina
2017-02-21  2:48 ` Linus Torvalds
2017-02-21  3:03   ` Linus Torvalds
2017-02-21  3:19     ` Linus Torvalds
2017-02-21  4:13     ` Linus Torvalds
2017-02-21  4:37       ` Linus Torvalds
2017-03-01  0:56         ` Linus Torvalds
2017-03-01  2:31           ` Andrew Duggan
2017-03-01  3:24             ` Peter Hutterer
2017-03-01  5:05               ` Linus Torvalds
2017-03-01  7:43                 ` Andrew Duggan
2017-03-01  9:03                 ` Benjamin Tissoires
2017-03-01  9:06                   ` Benjamin Tissoires
2017-03-01 17:31                     ` Dmitry Torokhov
2017-03-01 17:54                   ` Linus Torvalds
2017-03-01 17:58                     ` Dmitry Torokhov
2017-03-01 18:02                       ` Linus Torvalds
2017-02-21 14:17       ` [PATCH] HID: rmi: fallback to generic/multitouch if hid-rmi is not built (was Re: [GIT PULL] HID for 4.11) Jiri Kosina
2017-02-21 15:43         ` Linus Torvalds
2017-02-21 15:46           ` Jiri Kosina
2017-02-21 15:49             ` Linus Torvalds
2017-02-21 17:42               ` Benjamin Tissoires
2017-02-21 21:03                 ` Jiri Kosina
2017-02-22  0:53                   ` Jason Gerecke
2017-02-21 17:37         ` Benjamin Tissoires
2017-02-21 21:16         ` Andrew Duggan
2017-02-21  9:32   ` ath10k regression on XPS13 Kalle Valo
2017-02-21 18:18     ` David Miller
2017-02-21 18:38       ` Kalle Valo
2017-02-21 18:53         ` David Miller
2017-02-21 19:49           ` Kalle Valo
2017-02-21 21:00             ` David Miller
2017-02-21 18:52       ` Linus Torvalds
2017-02-21 21:01         ` David Miller [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=20170221.160103.272609294929297575.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ath10k@lists.infradead.org \
    --cc=jikos@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).