Re: early_printk accessing __log_buf
- From: Robin Getz <rgetz@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 Jul 2007 14:19:12 -0400
On Sun 22 Jul 2007 19:50, Mike Frysinger pondered:
i think the attached two functions account for what Robin and Andrew
were thinking ...
A note about why/when grab_lock would be set to zero (pre-kernel init, or
OOPs) might be nice.
Or - remove it - and tell people they should be using do_syslog interface in
a "normal" kernel environment (where log_end or log_start can be updated).
Either would be fine with me. Andrew?
-Robin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: early_printk accessing __log_buf
- From: Andrew Morton
- Re: early_printk accessing __log_buf
- References:
- early_printk accessing __log_buf
- From: Robin Getz
- Re: early_printk accessing __log_buf
- From: Robin Getz
- Re: early_printk accessing __log_buf
- From: Mike Frysinger
- early_printk accessing __log_buf
- Prev by Date: Re: [linux-pm] Power Management framework proposal
- Next by Date: Re: [linux-pm] Power Management framework proposal
- Previous by thread: Re: early_printk accessing __log_buf
- Next by thread: Re: early_printk accessing __log_buf
- Index(es):
Relevant Pages
|