From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Mirco Tischler <mt-ml@gmx.de>,
Leonid Podolny <leonidp.lists@gmail.com>,
linux-kernel@vger.kernel.org, yi.zhu@intel.com,
reinette.chatre@intel.com, linux-wireless@vger.kernel.org,
IvDoorn@gmail.com
Subject: Re: CPU load after killing iwlagn with RF kill switch
Date: Sun, 17 Aug 2008 13:07:14 -0400 [thread overview]
Message-ID: <20080817170714.GA29938@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240808170920r67e11567h2da8b396b18729dd@mail.gmail.com>
On Sun, Aug 17, 2008 at 07:20:54PM +0300, Tomas Winkler wrote:
> On Sun, Aug 17, 2008 at 6:02 PM, John W. Linville
> <linville@tuxdriver.com> wrote:
> > On Sun, Aug 17, 2008 at 10:04:12AM +0300, Tomas Winkler wrote:
> >
> >> There is gap in current rfkill implementation that we didn't close
> >> yet. There were also few patches that were not signed by Intel and
> >> are apparently wrong.
> >
> > Can you be more specific? Do you know which patches are wrong (even
> > if you don't know how to fix them)?
> >
>
> 80fcc9e28cf3a209fbfb39a7bbddc313c59c7424
> This one is wrong and there are more then are not acked even though
> they cause no problem. In general I would prefer that patches will be
> acked by Yi or me.
And in general, they are. In general I would prefer if you would
work upstream instead of working in iwlwifi-2.6 and periodically
dumping a dozen or more patches on me all at once. C'est la vie...
> I will try to rebase our rfkill fixes ASAP from iwlwifi-2.6. iwl5000 branch.
Thanks!
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-08-17 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A5EC02.4070303@gmail.com>
2008-08-17 1:59 ` CPU load after killing iwlagn with RF kill switch Mirco Tischler
2008-08-17 7:04 ` Tomas Winkler
2008-08-17 15:02 ` John W. Linville
2008-08-17 16:20 ` Tomas Winkler
2008-08-17 17:07 ` John W. Linville [this message]
2008-08-17 18:01 ` Tomas Winkler
2008-08-25 19:31 ` Luis R. Rodriguez
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=20080817170714.GA29938@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=IvDoorn@gmail.com \
--cc=leonidp.lists@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mt-ml@gmx.de \
--cc=reinette.chatre@intel.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@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 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).