From: hrhaan@gmail.com (Harro Haan)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v3 1/3] Fix soft lockup in at91 udc driver
Date: Wed, 3 Feb 2010 15:37:37 +0100 [thread overview]
Message-ID: <20100203143803.400254852@gmail.com> (raw)
In-Reply-To: 20100203143736.564974126@gmail.com
An embedded and charset-unspecified text was scrubbed...
Name: at91-usb-cdc-irq-lockup.patch
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100203/8443a1e4/attachment.el>
next prev parent reply other threads:[~2010-02-03 14:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 16:30 [patch 0/2] at91_udc driver: read_fifo timing issue + use spinlocks Harro Haan
2010-01-27 16:30 ` [patch 1/2] at91_udc.c read_fifo timing issue Harro Haan
2010-01-27 16:30 ` [patch 2/2] at91_udc.c use spinlocks instead of local_irq_xxx Harro Haan
2010-01-27 17:37 ` H Hartley Sweeten
2010-01-28 12:52 ` Harro Haan
2010-01-29 16:20 ` [patch v2 0/2] at91_udc driver: read_fifo timing issue + use spinlocks Harro Haan
2010-01-29 16:20 ` [patch v2 1/2] at91_udc.c read_fifo timing issue Harro Haan
2010-01-29 17:04 ` Remy Bohmer
2010-01-29 17:04 ` Remy Bohmer
2010-01-31 20:08 ` Ryan Mallon
2010-01-31 20:08 ` Ryan Mallon
2010-01-31 22:34 ` Anti Sullin
2010-01-31 22:34 ` Anti Sullin
2010-02-03 14:37 ` [patch v3 0/3] at91_udc: fix soft lockup, HW glitch and use spinlocks Harro Haan
2010-02-03 14:37 ` Harro Haan [this message]
2010-02-03 14:37 ` [patch v3 2/3] at91_udc HW glitch Harro Haan
2010-03-23 20:26 ` Andrew Victor
2010-03-23 20:26 ` Andrew Victor
2010-03-25 12:03 ` Harro Haan
2010-03-25 12:03 ` Harro Haan
2010-03-25 13:09 ` Anti Sullin
2010-03-25 13:09 ` Anti Sullin
2010-02-03 14:37 ` [patch v3 3/3] at91_udc.c use spinlocks instead of local_irq_xxx Harro Haan
2010-01-29 16:20 ` [patch v2 2/2] " Harro Haan
2010-01-29 17:27 ` H Hartley Sweeten
2010-01-29 17:27 ` H Hartley Sweeten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100203143803.400254852@gmail.com \
--to=hrhaan@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.