linux-kernel - Re: [PATCH] olpc-ec: initialise earlier

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] [day] [month] [year] [list]

Message-Id: <20130814151454.76650feb7f8095dabb1cf691@linux-foundation.org>
Date:	Wed, 14 Aug 2013 15:14:54 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Daniel Drake <dsd@...top.org>
Cc:	dilinger@...ued.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] olpc-ec: initialise earlier

On Sat, 10 Aug 2013 15:22:15 -0400 (EDT) Daniel Drake <dsd@...top.org> wrote:

> Being a low-level component, various drivers (e.g. olpc-battery) assume that
> it is ok to communicate with the OLPC Embedded Controller during probe.
> Therefore the OLPC EC driver must be initialised before other drivers try to
> use it. This was the case until it was recently moved out of arch/x86 and
> restructured.
> 
> Use arch_initcall so that olpc-ec is readied earlier, matching the
> previous behaviour. Fixes various drivers such as olpc-battery and
> olpc-xo1-sci.
> 

You imply that there was a regression, but don't describe the
user-visible effects of the regression.

You provide hints which would permit me, with sufficient effort, to
approximately work out which kernel versions were affected by the
regression and then left it at that.

I need to work out which kernel version(s) need patching, and why. 
Please, make it easier for me!

--
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/