linux-kernel - Re: CPU load after killing iwlagn with RF kill switch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 17 Aug 2008 13:07:14 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Tomas Winkler <tomasw@...il.com>
Cc:	Mirco Tischler <mt-ml@....de>,
	Leonid Podolny <leonidp.lists@...il.com>,
	linux-kernel@...r.kernel.org, yi.zhu@...el.com,
	reinette.chatre@...el.com, linux-wireless@...r.kernel.org,
	IvDoorn@...il.com
Subject: Re: CPU load after killing iwlagn with RF kill switch

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@...driver.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@...driver.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/