Dave, I just fixed this one in DRM CVS.
On Thu, 16 Sep 2004 00:13:46 -0700, Nishanth Aravamudan [EMAIL PROTECTED] wrote:
Re-submission of patch incorporating Alan Cox's suggestion of using
__set_current_state() and changing the other direct assignment in the
macro.
Thanks,
Nish
Nishanth Aravamudan wrote:
Any comments would be appreciated.
Description: Use set_current_state() instead of direct assignment of
current-state.
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
--- 2.6.9-rc1-mm4-vanilla/drivers/char/drm/drm_os_linux.h 2004-09-09
23:05:38.0
I'll apply this to my tree and fix up the rest of them in the DRM, and
push it to Linus..
Dave.
On Wed, 15 Sep 2004, Nishanth Aravamudan wrote:
Any comments would be appreciated.
Description: Use set_current_state() instead of direct assignment of
current-state.
Signed-off-by: Nishanth
On Iau, 2004-09-16 at 12:00, Dave Airlie wrote:
I'll apply this to my tree and fix up the rest of them in the DRM, and
push it to Linus..
Use __set_current_state() for these. set_current_state also includes a
memory barrier (ie its designed to be safe for all uses) while the DRI
code is already
Re-submission of patch incorporating Alan Cox's suggestion of using
__set_current_state() and changing the other direct assignment in the
macro.
Thanks,
Nish
Description: Use set_current_state() instead of direct assignment of
current-state.
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
Any comments would be appreciated.
Description: Use set_current_state() instead of direct assignment of
current-state.
Signed-off-by: Nishanth Aravamudan [EMAIL PROTECTED]
--- 2.6.9-rc1-mm4-vanilla/drivers/char/drm/drm_os_linux.h 2004-09-09
23:05:38.0 -0700
+++
