From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: [patch 0/3] musb_hdrc, remove MGC_{Read,Write}Csr{8,16}
Date: Thu, 18 Jan 2007 15:35:07 -0800 [thread overview]
Message-ID: <200701181535.08332.david-b@pacbell.net> (raw)
Folowing this are three patches removing those annoying CaMeLcAsE
macros cluttering up the sources ... this is the last significant
such fix that's needed IMO, although certainly struct members,
variables, and function/procedure parameters can be cleaned up.
Given that, issues I know about on the musb_hdrc code in GIT right
now, observed on tusb6010 but not tested on DaVinci, include:
- Hmm, host side was not enumerating ... new failure
- DMA wierdness of various types
- Various issues with suspend states and remote wakeup
That list is just so anyone running into them needn't be too
surprised.
- Dave
next reply other threads:[~2007-01-18 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 23:35 David Brownell [this message]
2007-01-19 0:03 ` [patch 0/3] musb_hdrc, remove MGC_{Read,Write}Csr{8,16} Tony Lindgren
2007-01-19 3:31 ` David Brownell
2007-01-19 23:49 ` David Brownell
2007-01-22 21:19 ` Tony Lindgren
2007-01-22 21:59 ` David Brownell
2007-01-22 22:45 ` Tony Lindgren
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=200701181535.08332.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.com \
/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