On Wed, Dec 12, 2012 at 02:56:47AM +0100, Hans J. Koch wrote:
> On Tue, Dec 11, 2012 at 03:18:16PM -0800, Greg KH wrote:
> > On Wed, Dec 12, 2012 at 12:12:01AM +0100, Benedikt Spranger wrote:
> > > The documentation has no clear statement to the POSIX 1003.1 mmap()
> > > feature, wich allows open()
On Wed, Dec 12, 2012 at 01:45:34AM +0100, Benedikt Spranger wrote:
> On Tue, 11 Dec 2012 15:18:16 -0800
> Greg KH wrote:
>
> > > -open(), you will probably also want a custom
> > > +release(), you will probably also want a
> > > custom release() function.
> > That sentance no longer makes sense.
On Tue, Dec 11, 2012 at 03:18:16PM -0800, Greg KH wrote:
> On Wed, Dec 12, 2012 at 12:12:01AM +0100, Benedikt Spranger wrote:
> > The documentation has no clear statement to the POSIX 1003.1 mmap()
> > feature, wich allows open(), mmap(), close() while the mmaped pointer is
> > valid.
> > The rele
On Tue, 11 Dec 2012 15:18:16 -0800
Greg KH wrote:
> > -open(), you will probably also want a custom
> > +release(), you will probably also want a
> > custom release() function.
> That sentance no longer makes sense.
DUH! will fix...
> > +CAVE: The release hook may be processed, even if a
> > mm
On Wed, Dec 12, 2012 at 12:12:01AM +0100, Benedikt Spranger wrote:
> The documentation has no clear statement to the POSIX 1003.1 mmap()
> feature, wich allows open(), mmap(), close() while the mmaped pointer is
> valid.
> The release() hook inveigled driver programmer to activate owermanagement
>
The documentation has no clear statement to the POSIX 1003.1 mmap()
feature, wich allows open(), mmap(), close() while the mmaped pointer is valid.
The release() hook inveigled driver programmer to activate owermanagement
functuonality in the release hook. This may harm.
Signed-off-by: Benedikt Sp
6 matches
Mail list logo
