linux-kernel - Re: zaurus: cleanup sharpsl

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]

Message-ID: <20091022191954.GB6611@elf.ucw.cz>
Date:	Thu, 22 Oct 2009 21:19:55 +0200
From:	Pavel Machek <pavel@....cz>
To:	Eric Miao <eric.y.miao@...il.com>
Cc:	rpurdie@...ys.net, lenz@...wisc.edu,
	kernel list <linux-kernel@...r.kernel.org>,
	Dirk@...er-online.de, arminlitzel@....de,
	Cyril Hrubis <metan@....cz>, thommycheck@...il.com,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	dbaryshkov@...il.com, omegamoon@...il.com, utx@...guin.cz
Subject: Re: zaurus: cleanup sharpsl_pm.c

On Fri 2009-10-23 02:26:55, Eric Miao wrote:
> > Introduce separate set of battery limits for corgi. This fixes
> > compilation, and the values probably should be subtly different, too.
> 
> [Why I'm receiving this for twice ....?]

No idea. Perhaps once from maillist?

> Pavel,
> 
> Anyway, I was thinkin maybe we need a shared table before there
> are real requirements for different machines to have their own?

Well, I'd say that the sharing leads to some very ugly code. ... so
I'd preer it unshared.

But if you would prefer, I can prepare patch without the table
moving...?

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/