From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] usbuhci.c bug?
Date: Tue, 16 Feb 2016 08:42:35 +0100 [thread overview]
Message-ID: <3b3835e4be155ddbd5f73b7c8c7ee35f@felloff.net> (raw)
In-Reply-To: <b49be407b1e7cab50d06ff046fd77718@mars.jitaku.localdomain>
if the controller has the run bit always clear, but appears to be working,
we could move the check in the debug case. i can see how printing every time
in the interrupt handler would make your system pretty much unusable.
--
cinap
next prev parent reply other threads:[~2016-02-16 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 22:19 kokamoto
2016-02-16 7:29 ` [9front] " cinap_lenrek
2016-02-15 23:20 ` kokamoto
2016-02-16 7:42 ` cinap_lenrek [this message]
2016-02-16 7:49 ` cinap_lenrek
2016-02-16 7:52 ` cinap_lenrek
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=3b3835e4be155ddbd5f73b7c8c7ee35f@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).