Hi,
This continues from my previous thread (subject line "All architecture
maintainers: pgd_alloc()" on lkml), and for Linus' sake, here is the
explaination I supplied:
| For ARM, I require pgd_alloc to take a struct mm_struct argument (so the
| pgd_alloc prototype becomes "pgd_t *pgd_alloc(stru
Andrea Arcangeli writes:
> That it is allowed by my generic code that does spin_lock_irq in down_* and
> spin_lock_irqsave in up_* but it's disallowed by the weaker semantics of the
> generic and x86 semaphores 2.4.4pre[2345] (or + David's last patch).
Hang on, who's code is in 2.4.4-pre5? It cl
Tom Leete writes:
> $ diff -6 ...
> will give 6 lines of context. patch will understand the output without any
> extra help.
Indeed, but I can't do that to a patch that Alan or Linus produces.
--
Russell King ([EMAIL PROTECTED])The developer of ARM Linux
http://www.a
Eric,
Please apply this patch before doing anything in the ARM tree.
What you will find is that most of your symbols in these files were due
to it being out of date. However, I'd say the bigger problem is the
symbols that don't exist.
Also, you may not have the full story of the Config.in file
Eric S. Raymond writes:
> > The ones that show up in arch/arm/def-configs are purely because I've been
> > keeping back the updates to these files; each time the config structure
> > changes, I get a nice big patch from people with the new def-configs. I
> > didn't want to inflict this too regula
Jesse Pollard writes:
> Absolutely true. The only help the checksumming etc stuff is good for is
> detecting the fact afterward by external comparison.
Don't we already have that to some extent? rpm -ya or rpm -y
on a RedHat system? I'm sure that there is a Debian equivalent.
--
Russell King
> Aiee, killing interrupt handler
> invalid operand:
> CPU:0
> EIP:0010:[]
> EFLAGS: 00010292
>...
> Aiee, killing interrupt handler
> invalid operand:
> CPU:0
> EIP:0010:[]
> EFLAGS: 00010286
You are not the only one to find this. On the ARM kernels, I have had to
chan
7 matches
Mail list logo
