[PATCH v2 5/5] xhci: Remove recursive call to xhci_handle_event

Make the caller loop while there are events to handle, instead. Signed-off-by: Matt Evans --- 1 byte smaller after Sergei's suggestion. drivers/usb/host/xhci-ring.c | 16 +--- 1 files changed, 9 insertions(+), 7 deletions(-) diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb

[PATCH v2 3/5] xhci: Add rmb() between reading event validity & event data access.

On weakly-ordered systems, the reading of an event's content must occur after reading the event's validity. Signed-off-by: Matt Evans --- Segher, thanks for the comment; explanation added. drivers/usb/host/xhci-ring.c |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/

Re: Early kernel debugging

On Sun, 2011-03-27 at 20:00 +0200, Philipp Ittershagen wrote: > On 03/25/2011 09:50 AM, Guillaume Dargaud wrote: > > Hello all, > > what can you do when the kernel you try to run stops before printing > > anything on the console ? > > http://elinux.org/Kernel_Debugging_Tips#Debugging_early_boot_p

Re: Early kernel debugging

On 03/25/2011 09:50 AM, Guillaume Dargaud wrote: > Hello all, > what can you do when the kernel you try to run stops before printing anything > on the console ? http://elinux.org/Kernel_Debugging_Tips#Debugging_early_boot_problems Basically it means connecting a debugger to the running kernel (u