[PATCH 2/2] DRM: use anon_inode instead of delayed inode init

2013-10-02 Thread David Herrmann
Instead of delaying inode initialization until first ->open(), we can use an anonymous inode. This avoids modifying FS internal inode fields and provides us a private address_space right during initialization. Delayed TTM dev_mapping initialization is currently left untouched to keep this simple.

[PATCH 2/2] DRM: use anon_inode instead of delayed inode init

2013-07-11 Thread Daniel Vetter
On Thu, Jul 11, 2013 at 01:45:30AM +0200, David Herrmann wrote: > Instead of delaying inode initialization until first ->open(), we can use > an anonymous inode. This avoids modifying FS internal inode fields and > provides us a private address_space right during initialization. > > Delayed TTM de

[PATCH 2/2] DRM: use anon_inode instead of delayed inode init

2013-07-11 Thread David Herrmann
Instead of delaying inode initialization until first ->open(), we can use an anonymous inode. This avoids modifying FS internal inode fields and provides us a private address_space right during initialization. Delayed TTM dev_mapping initialization is currently left untouched to keep this simple.

Re: [PATCH 2/2] DRM: use anon_inode instead of delayed inode init

2013-07-11 Thread Daniel Vetter
On Thu, Jul 11, 2013 at 01:45:30AM +0200, David Herrmann wrote: > Instead of delaying inode initialization until first ->open(), we can use > an anonymous inode. This avoids modifying FS internal inode fields and > provides us a private address_space right during initialization. > > Delayed TTM de

[PATCH 2/2] DRM: use anon_inode instead of delayed inode init

2013-07-10 Thread David Herrmann
Instead of delaying inode initialization until first ->open(), we can use an anonymous inode. This avoids modifying FS internal inode fields and provides us a private address_space right during initialization. Delayed TTM dev_mapping initialization is currently left untouched to keep this simple.