From: "Jakub Kiciński" <moorray3@wp.pl>
To: <gmoutso@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mediatek mt7630e and ksoftirqd CPU load
Date: Wed, 1 Apr 2015 22:01:33 +0200 [thread overview]
Message-ID: <20150401220133.41149f15@north> (raw)
In-Reply-To: <551c496d.6465b40a.3fc0.26b7@mx.google.com>
On Wed, 1 Apr 2015 19:33:13 +0000, gmoutso@gmail.com wrote:
> Thank you very much for your reply.
>
> https://github.com/kuba-moo/mt7630e solves my 100% CPU problem.
>
> I will publicize your repository on the Ubuntu bug
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1220146
>
> If you don’t mind. You will make many people like me happy!
Glad to hear that it works for you.
prev parent reply other threads:[~2015-04-01 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 16:12 mediatek mt7630e and ksoftirqd CPU load George Moutsopoulos
2015-03-26 16:44 ` Larry Finger
2015-03-26 16:56 ` George Moutsopoulos
2015-04-01 16:05 ` Jakub Kiciński
[not found] ` <551c496d.6465b40a.3fc0.26b7@mx.google.com>
2015-04-01 20:01 ` Jakub Kiciński [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=20150401220133.41149f15@north \
--to=moorray3@wp.pl \
--cc=Larry.Finger@lwfinger.net \
--cc=gmoutso@gmail.com \
--cc=linux-wireless@vger.kernel.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).