18 May, 2010
1 commit
-
Use kzalloc rather than the combination of kmalloc and memset.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)//
@@
expression x,size,flags;
statement S;
@@-x = kmalloc(size,flags);
+x = kzalloc(size,flags);
if (x == NULL) S
-memset(x, 0, size);
//Signed-off-by: Julia Lawall
Reviewed-by: Corbin Simpson
Reviewed-by: Matt Turner
Signed-off-by: Dave Airlie
19 Jun, 2009
1 commit
-
It hasn't been used in ages, and having the user tell your how much
memory is being freed at free time is a recipe for disaster even if it
was ever used.Signed-off-by: Eric Anholt
29 Dec, 2008
1 commit
-
This is step one towards having multiple masters sharing a drm
device in order to get fast-user-switching to work.It splits out the information associated with the drm master
into a separate kref counted structure, and allocates this when
a master opens the device node. It also allows the current master
to abdicate (say while VT switched), and a new master to take over
the hardware.It moves the Intel and radeon drivers to using the sarea from
within the new master structures.Signed-off-by: Dave Airlie
14 Jul, 2008
1 commit
-
With the coming of kernel based modesetting and the memory manager stuff,
the everything in one directory approach was getting very ugly and
starting to be unmanageable.This restructures the drm along the lines of other kernel components.
It creates a drivers/gpu/drm directory and moves the hw drivers into
subdirectores. It moves the includes into an include/drm, and
sets up the unifdef for the userspace headers we should be exporting.Signed-off-by: Dave Airlie