I've been trying this a few months ago, ( https://lkml.org/lkml/2014/10/8/98 )
in a very bad attempt that (thankfully) failed.
I'm happy to see you trying this now and got the change in drivers/fuse
merged now. I've been running a kernel with this change for quite some time,
it's obviously fine.
I've been trying this a few months ago, ( https://lkml.org/lkml/2014/10/8/98 )
in a very bad attempt that (thankfully) failed.
I'm happy to see you trying this now and got the change in drivers/fuse
merged now. I've been running a kernel with this change for quite some time,
it's obviously fine.
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file->private_data for other file
operations to use (given the user calls open()).
This leads to situations where a miscdevice
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file-private_data for other file
operations to use (given the user calls open()).
This leads to situations where a miscdevice
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file->private_data for other file
operations to use (given the user calls open()).
This leads to situations where a miscdevice
Am 2014-10-09 17:50, schrieb Greg KH:
> On Thu, Oct 09, 2014 at 03:10:21PM +0200, Martin Kepplinger wrote:
>> Am 2014-10-08 15:43, schrieb Greg KH:
>>> On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
Am 2014-10-09 17:50, schrieb Greg KH:
On Thu, Oct 09, 2014 at 03:10:21PM +0200, Martin Kepplinger wrote:
Am 2014-10-08 15:43, schrieb Greg KH:
On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
the open() file
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file-private_data for other file
operations to use (given the user calls open()).
This leads to situations where a miscdevice
Am 2014-10-09 17:50, schrieb Greg KH:
> On Thu, Oct 09, 2014 at 03:10:21PM +0200, Martin Kepplinger wrote:
>> Am 2014-10-08 15:43, schrieb Greg KH:
>>> On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
Am 2014-10-09 17:50, schrieb Greg KH:
On Thu, Oct 09, 2014 at 03:10:21PM +0200, Martin Kepplinger wrote:
Am 2014-10-08 15:43, schrieb Greg KH:
On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
the open() file
On Thu, Oct 09, 2014 at 03:10:21PM +0200, Martin Kepplinger wrote:
> Am 2014-10-08 15:43, schrieb Greg KH:
> > On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
> >> As of now, a miscdevice driver has to provide an implementation of
> >> the open() file operation if it wants to
Am 2014-10-08 15:43, schrieb Greg KH:
> On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
>> As of now, a miscdevice driver has to provide an implementation of
>> the open() file operation if it wants to have misc_open() assign a
>> pointer to struct miscdevice to
Am 2014-10-08 15:43, schrieb Greg KH:
On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file-private_data for
On Thu, Oct 09, 2014 at 03:10:21PM +0200, Martin Kepplinger wrote:
Am 2014-10-08 15:43, schrieb Greg KH:
On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have
On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
> As of now, a miscdevice driver has to provide an implementation of
> the open() file operation if it wants to have misc_open() assign a
> pointer to struct miscdevice to file->private_data for other file
> operations to use
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file->private_data for other file
operations to use (given the user calls open()).
This leads to situations where a miscdevice
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file-private_data for other file
operations to use (given the user calls open()).
This leads to situations where a miscdevice
On Wed, Oct 08, 2014 at 10:47:54AM +0200, Martin Kepplinger wrote:
As of now, a miscdevice driver has to provide an implementation of
the open() file operation if it wants to have misc_open() assign a
pointer to struct miscdevice to file-private_data for other file
operations to use (given the
18 matches
Mail list logo
