Am 18.01.21 um 08:49 schrieb Eli Cohen:
On Mon, Jan 18, 2021 at 08:43:12AM +0100, Christian König wrote:
Hi Eli,
have you already tried using kmemleak?
This sounds like a leak of memory allocated using kmalloc(), so kmemleak
should be able to catch it.
Hi Christian,
I have the following con
Hi
Am 18.01.21 um 08:43 schrieb Christian König:
Hi Eli,
have you already tried using kmemleak?
This sounds like a leak of memory allocated using kmalloc(), so kmemleak
should be able to catch it.
I have an idea what happens here. When the refcount is 0 in kmap, a new
page mapping for the
On Mon, Jan 18, 2021 at 7:53 AM Thomas Zimmermann wrote:
>
> Hi
>
> Am 18.01.21 um 02:22 schrieb ZhiJie.Zhang:
> > From: zhangzhijie
> >
> > this callback was used by drm_kms_helper_hotplug_event()
> >
> > V2: (Thanks for Daniel's suggestions)
> > - remove the FIXME below.since with the drm_clien
Hi Eli,
have you already tried using kmemleak?
This sounds like a leak of memory allocated using kmalloc(), so kmemleak
should be able to catch it.
Regards,
Christian.
Am 17.01.21 um 06:08 schrieb Eli Cohen:
On Fri, Jan 15, 2021 at 10:03:50AM +0100, Thomas Zimmermann wrote:
Could you pleas
Hi
Am 18.01.21 um 02:22 schrieb ZhiJie.Zhang:
From: zhangzhijie
this callback was used by drm_kms_helper_hotplug_event()
V2: (Thanks for Daniel's suggestions)
- remove the FIXME below.since with the drm_client
- infrastructure and the generic fbdev emulation we've
- resolved this all very nea
From: zhangzhijie
this callback was used by drm_kms_helper_hotplug_event()
V2: (Thanks for Daniel's suggestions)
- remove the FIXME below.since with the drm_client
- infrastructure and the generic fbdev emulation we've
- resolved this all very neatly now.
V3: Add comments that This hook is depr
On Mon, 18 Jan 2021 at 10:59, Stephen Rothwell wrote:
>
> Hi all,
>
> On Mon, 11 Jan 2021 10:56:54 +1100 Stephen Rothwell
> wrote:
> >
> > On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell
> > wrote:
> > >
> > > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell
> > > wrote:
> > > >
> > > >
Hi all,
On Mon, 11 Jan 2021 10:56:54 +1100 Stephen Rothwell
wrote:
>
> On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell
> wrote:
> >
> > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell
> > wrote:
> > >
> > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
>
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
between commits:
3c517ca5212f ("Revert "drm/amdgpu/disply: fix documentation warnings in
display manager"")
a7ddd22151fc ("Revert "drm/amd/display: Expose new CRC window
--
Thanks & Regards,
Aurabindo Pillai
On Wed, Jan 6, 2021 at 15:02, "Kazlauskas, Nicholas"
wrote:
On 2021-01-04 4:08 p.m., Aurabindo Pillai wrote:
[Why&How]
Inorder to enable freesync video mode, driver adds extra
modes based on preferred modes for common freesync frame rates.
When commiti
https://bugzilla.kernel.org/show_bug.cgi?id=211189
Dominik Mierzejewski (domi...@greysector.net) changed:
What|Removed |Added
Tree|Mainline|Fedora
--
11 matches
Mail list logo