From: David Brownell <david-b@pacbell.net>
To: pavel@ucw.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re(2): fix u32 vs. pm message t in usb
Date: Sun, 3 Apr 2005 12:01:02 -0800 [thread overview]
Message-ID: <200504031301.02179.david-b@pacbell.net> (raw)
In-Reply-To: <20050403193216.961D5194084@smtp.etmail.cz>
On Sunday 03 April 2005 12:31 pm, pavel@ucw.cz wrote:
> Okay, you obviously have easy access to usb development trees...
> Do you think you could just take this patch as a basis and fix
> remaining u32 vs pm-message-t in usb? --p
Fixing the "sparse -Wbitwise" messages, and addressing some other
behavior changes/bugs that crept in, was the idea. That's already
done, but _without_ taking this as a basis (or breaking the sysfs
support etc).
The patches I sent fix everything I had time to test (just a subset
of the dozens of cases previously tested, probably covering the main
stuff that got broken) except the non-PCI platform_bus drivers where
pm_message_t has discarded essential functionality. (Notably, info
about whether device clocks and/or power must be turned off.)
Fixing those will be more work than seems reasonable for 2.6.12
kernels. Among other things, there's still a lot of stuff that
needs to percolate out to arch trees; designing and testing such
fixes takes time, as does percolating it back.
- Dave
p.s. PCI-express patches don't belong with USB patches. :)
next parent reply other threads:[~2005-04-03 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050403193216.961D5194084@smtp.etmail.cz>
2005-04-03 20:01 ` David Brownell [this message]
2005-04-03 22:57 ` Re(2): fix u32 vs. pm message t in usb Pavel Machek
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=200504031301.02179.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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