* Jan Kiszka <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> > In any case, if there are any open issues we are very much ready and
> > willing to address them now or after any potential upstream merge of
> > this codebase. This has meanwhile become one of the best-reviewed pieces
> > of ker
Ingo Molnar wrote:
> In any case, if there are any open issues we are very much ready and
> willing to address them now or after any potential upstream merge of
> this codebase. This has meanwhile become one of the best-reviewed pieces
> of kernel code in living memory ;-)
>
I spotted one... :
> after a quick glance i'm happy to conclude that all but one of Andi's
At least the weird in_interrupt_stack() code seems to be still
in there.
I also still see a lot of open coded hex manipulation.
The synchronization code looks as bad as it was before.
The getthread magic pids are also stil
3 matches
Mail list logo
