On Wed, Feb 21, 2018 at 03:30:41PM +0100, Thierry Reding wrote:
> On Wed, Feb 21, 2018 at 02:15:13PM +0100, Lukas Wunner wrote:
> > On Wed, Feb 21, 2018 at 01:30:23PM +0200, Jyri Sarha wrote:
> > > On 21/02/18 09:18, Lukas Wunner wrote:
> > > > On Tue, Feb 20, 2018 at 05:04:00PM +0200, Jyri Sarha
On Wed, Feb 21, 2018 at 02:15:13PM +0100, Lukas Wunner wrote:
> On Wed, Feb 21, 2018 at 01:30:23PM +0200, Jyri Sarha wrote:
> > On 21/02/18 09:18, Lukas Wunner wrote:
> > > On Tue, Feb 20, 2018 at 05:04:00PM +0200, Jyri Sarha wrote:
> > >> On 20/02/18 14:03, Thierry Reding wrote:
> > >>> On Tue,
On Wed, Feb 21, 2018 at 08:18:42AM +0100, Lukas Wunner wrote:
> [+cc Rafael]
>
> On Tue, Feb 20, 2018 at 05:04:00PM +0200, Jyri Sarha wrote:
> > On 20/02/18 14:03, Thierry Reding wrote:
> > > On Tue, Feb 20, 2018 at 01:28:48PM +0200, Jyri Sarha wrote:
> > >> On 20/02/18 12:34, Thierry Reding
On Wed, Feb 21, 2018 at 01:30:23PM +0200, Jyri Sarha wrote:
> On 21/02/18 09:18, Lukas Wunner wrote:
> > On Tue, Feb 20, 2018 at 05:04:00PM +0200, Jyri Sarha wrote:
> >> On 20/02/18 14:03, Thierry Reding wrote:
> >>> On Tue, Feb 20, 2018 at 01:28:48PM +0200, Jyri Sarha wrote:
> On 20/02/18
On 21/02/18 09:18, Lukas Wunner wrote:
> [+cc Rafael]
>
> On Tue, Feb 20, 2018 at 05:04:00PM +0200, Jyri Sarha wrote:
>> On 20/02/18 14:03, Thierry Reding wrote:
>>> On Tue, Feb 20, 2018 at 01:28:48PM +0200, Jyri Sarha wrote:
On 20/02/18 12:34, Thierry Reding wrote:
>> On Mon, Feb 19,
[+cc Rafael]
On Tue, Feb 20, 2018 at 05:04:00PM +0200, Jyri Sarha wrote:
> On 20/02/18 14:03, Thierry Reding wrote:
> > On Tue, Feb 20, 2018 at 01:28:48PM +0200, Jyri Sarha wrote:
> >> On 20/02/18 12:34, Thierry Reding wrote:
> On Mon, Feb 19, 2018 at 10:06:22PM +0200, Jyri Sarha wrote:
>
On 20/02/18 14:03, Thierry Reding wrote:
> On Tue, Feb 20, 2018 at 01:28:48PM +0200, Jyri Sarha wrote:
>> On 20/02/18 12:34, Thierry Reding wrote:
>>> On Mon, Feb 19, 2018 at 11:59:23PM +0100, Daniel Vetter wrote:
On Mon, Feb 19, 2018 at 10:06:22PM +0200, Jyri Sarha wrote:
> Currently
On Tue, Feb 20, 2018 at 01:28:48PM +0200, Jyri Sarha wrote:
> On 20/02/18 12:34, Thierry Reding wrote:
> > On Mon, Feb 19, 2018 at 11:59:23PM +0100, Daniel Vetter wrote:
> >> On Mon, Feb 19, 2018 at 10:06:22PM +0200, Jyri Sarha wrote:
> >>> Currently there is no way for a master drm driver to
On 20/02/18 12:34, Thierry Reding wrote:
> On Mon, Feb 19, 2018 at 11:59:23PM +0100, Daniel Vetter wrote:
>> On Mon, Feb 19, 2018 at 10:06:22PM +0200, Jyri Sarha wrote:
>>> Currently there is no way for a master drm driver to protect against an
>>> attached panel driver from being unloaded while
On Mon, Feb 19, 2018 at 11:59:23PM +0100, Daniel Vetter wrote:
> On Mon, Feb 19, 2018 at 10:06:22PM +0200, Jyri Sarha wrote:
> > Currently there is no way for a master drm driver to protect against an
> > attached panel driver from being unloaded while it is in use. The
> > least we can do is to
On Mon, Feb 19, 2018 at 10:06:22PM +0200, Jyri Sarha wrote:
> Currently there is no way for a master drm driver to protect against an
> attached panel driver from being unloaded while it is in use. The
> least we can do is to indicate the usage by incrementing the module
> reference count.
>
>
Currently there is no way for a master drm driver to protect against an
attached panel driver from being unloaded while it is in use. The
least we can do is to indicate the usage by incrementing the module
reference count.
Signed-off-by: Jyri Sarha
cc: e...@anholt.net
cc:
12 matches
Mail list logo