Sergei Shtylyov wrote:
> Since it doesn't make sense both to set kgdb_may_fault flag before setting up
> the jump buffer and to resotre the preempt count if a fault hasn't happened,
> get rid of kgdb_[un]set_may_fault() introducing the inline wrapper around
> kgdb_fault_setjmp() call to enable the kernel faults and save/restore the
> preempt count if the preemption is enabled (removing kgdb_fault_preempt_count
> global variable at the same time) and directly clearing kgdb_may_fault on the
> normal, non-faulted exit path from the memory manipulation functions...
>
> Also, while at it, do some more cleanups:
>
> - add newlines after block declarations;
>
> - get rid of unneeded braces;
>
> - clean up grammar/style in comments...
>
> Signed-off-by: Sergei Shtylyov <[EMAIL PROTECTED]>
>
>   
This has been merged to the 2.6.21 into core-lite uprev branch and 
upstreamed into the for_mm branch in kernel.org.

I have a number of other patches in the queue to review as well, so more 
changes to come.

Cheers,
Jason.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to