All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PULL] drm-misc-fixes
Date: Tue, 13 Jul 2021 15:44:34 +0200	[thread overview]
Message-ID: <YO2Ywqla3CgS+AbL@phenom.ffwll.local> (raw)
In-Reply-To: <YO07pEfweKVO+7y0@linux-uq9g>

On Tue, Jul 13, 2021 at 10:44:05AM +0200, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> these two fixes in drm-misc-fixes got lost during last cycle. Sending them
> now.

Applied to drm-fixes, thanks.
-Daniel

> 
> Best regards
> Thomas
> 
> drm-misc-fixes-2021-07-13:
> Short summary of fixes pull:
> 
>  * dma-buf: Fix fence leak in sync_file_merge() error code
>  * drm/panel: nt35510: Don't fail on DSI reads
> The following changes since commit d330099115597bbc238d6758a4930e72b49ea9ba:
> 
>   drm/nouveau: fix dma_address check for CPU/GPU sync (2021-06-24 15:40:44 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-fixes-2021-07-13
> 
> for you to fetch changes up to ffe000217c5068c5da07ccb1c0f8cce7ad767435:
> 
>   dma-buf/sync_file: Don't leak fences on merge failure (2021-07-12 13:34:49 +0200)
> 
> ----------------------------------------------------------------
> Short summary of fixes pull:
> 
>  * dma-buf: Fix fence leak in sync_file_merge() error code
>  * drm/panel: nt35510: Don't fail on DSI reads
> 
> ----------------------------------------------------------------
> Jason Ekstrand (1):
>       dma-buf/sync_file: Don't leak fences on merge failure
> 
> Linus Walleij (1):
>       drm/panel: nt35510: Do not fail if DSI read fails
> 
>  drivers/dma-buf/sync_file.c                   | 13 +++++++------
>  drivers/gpu/drm/panel/panel-novatek-nt35510.c |  4 +---
>  2 files changed, 8 insertions(+), 9 deletions(-)
> 
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer
> 
> -- 
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: dim-tools@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Sean Paul <sean@poorly.run>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PULL] drm-misc-fixes
Date: Tue, 13 Jul 2021 15:44:34 +0200	[thread overview]
Message-ID: <YO2Ywqla3CgS+AbL@phenom.ffwll.local> (raw)
In-Reply-To: <YO07pEfweKVO+7y0@linux-uq9g>

On Tue, Jul 13, 2021 at 10:44:05AM +0200, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> these two fixes in drm-misc-fixes got lost during last cycle. Sending them
> now.

Applied to drm-fixes, thanks.
-Daniel

> 
> Best regards
> Thomas
> 
> drm-misc-fixes-2021-07-13:
> Short summary of fixes pull:
> 
>  * dma-buf: Fix fence leak in sync_file_merge() error code
>  * drm/panel: nt35510: Don't fail on DSI reads
> The following changes since commit d330099115597bbc238d6758a4930e72b49ea9ba:
> 
>   drm/nouveau: fix dma_address check for CPU/GPU sync (2021-06-24 15:40:44 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-fixes-2021-07-13
> 
> for you to fetch changes up to ffe000217c5068c5da07ccb1c0f8cce7ad767435:
> 
>   dma-buf/sync_file: Don't leak fences on merge failure (2021-07-12 13:34:49 +0200)
> 
> ----------------------------------------------------------------
> Short summary of fixes pull:
> 
>  * dma-buf: Fix fence leak in sync_file_merge() error code
>  * drm/panel: nt35510: Don't fail on DSI reads
> 
> ----------------------------------------------------------------
> Jason Ekstrand (1):
>       dma-buf/sync_file: Don't leak fences on merge failure
> 
> Linus Walleij (1):
>       drm/panel: nt35510: Do not fail if DSI read fails
> 
>  drivers/dma-buf/sync_file.c                   | 13 +++++++------
>  drivers/gpu/drm/panel/panel-novatek-nt35510.c |  4 +---
>  2 files changed, 8 insertions(+), 9 deletions(-)
> 
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer
> 
> -- 
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2021-07-13 13:44 UTC|newest]

Thread overview: 188+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13  8:44 [Intel-gfx] [PULL] drm-misc-fixes Thomas Zimmermann
2021-07-13  8:44 ` Thomas Zimmermann
2021-07-13 13:44 ` Daniel Vetter [this message]
2021-07-13 13:44   ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29 19:51 [Intel-gfx] " Maarten Lankhorst
2023-11-23 12:22 Maarten Lankhorst
2023-11-16 13:48 Maarten Lankhorst
2023-11-17 10:45 ` Daniel Vetter
2023-11-08 13:18 Maarten Lankhorst
2023-11-10 20:33 ` Daniel Vetter
2023-11-02 13:00 Thomas Zimmermann
2023-10-26 11:01 Thomas Zimmermann
2023-10-19 11:46 Thomas Zimmermann
2023-10-12 11:16 Thomas Zimmermann
2023-10-05  9:26 Thomas Zimmermann
2023-09-28  8:12 Thomas Zimmermann
2023-09-21 15:37 Thomas Zimmermann
2023-09-14 12:26 Thomas Zimmermann
2023-09-07  7:44 Maxime Ripard
2023-08-24  8:41 Maxime Ripard
2023-08-17 13:38 Maxime Ripard
2023-08-10  6:52 Maxime Ripard
2023-08-03  7:39 Maxime Ripard
2023-07-27  7:05 Maxime Ripard
2023-07-20  7:58 Maxime Ripard
2023-07-13  8:17 Maxime Ripard
2023-07-07  7:23 Thomas Zimmermann
2023-06-21 19:43 Maarten Lankhorst
2023-06-16 11:32 Maarten Lankhorst
2023-06-08  8:41 [Intel-gfx] [PULL] drm-intel-fixes Joonas Lahtinen
2023-06-08  8:45 ` [Intel-gfx] [PULL] drm-MISC-fixes Maarten Lankhorst
2023-06-08  8:50   ` Jani Nikula
2023-06-08  9:24     ` Maarten Lankhorst
2023-04-26  5:59 [Intel-gfx] [PULL] drm-misc-fixes Maarten Lankhorst
2023-05-11  8:01 ` Thomas Zimmermann
2023-05-11 10:04   ` Maarten Lankhorst
2023-04-20  8:31 Thomas Zimmermann
2023-04-13 18:42 Thomas Zimmermann
2023-04-13 19:27 ` Daniel Vetter
2023-04-05 18:28 Thomas Zimmermann
2023-04-05 19:10 ` Daniel Vetter
2023-03-30 14:10 Thomas Zimmermann
2023-03-30 17:52 ` Daniel Vetter
2023-03-23  8:24 Thomas Zimmermann
2023-03-24  9:17 ` Daniel Vetter
2023-03-16 14:33 Thomas Zimmermann
2023-02-23  8:38 Maxime Ripard
2023-02-16  9:19 Maxime Ripard
2023-02-09  8:36 Maxime Ripard
2023-02-02  8:57 Maxime Ripard
2023-01-26 10:40 Maxime Ripard
2023-01-19  8:20 Maxime Ripard
2023-01-12 13:09 Maxime Ripard
2023-01-05  7:49 Maxime Ripard
2023-01-05 10:10 ` Daniel Vetter
2022-12-22 13:02 Maxime Ripard
2022-11-30 13:16 Maarten Lankhorst
2022-11-30 13:43 ` Maxime Ripard
2022-11-30 14:10   ` Daniel Vetter
2022-11-24 10:26 Maarten Lankhorst
2022-11-17 18:30 Maarten Lankhorst
2022-11-09 16:22 Maarten Lankhorst
2022-11-02 21:59 Maarten Lankhorst
2022-10-27 10:00 Maarten Lankhorst
2022-10-20 11:34 Maarten Lankhorst
2022-10-13 12:37 Thomas Zimmermann
2022-09-29 14:43 Thomas Zimmermann
2022-09-22 14:12 Thomas Zimmermann
2022-09-15 12:03 Thomas Zimmermann
2022-09-08 12:38 Thomas Zimmermann
2022-08-31 18:33 Thomas Zimmermann
2022-08-25  7:31 Thomas Zimmermann
2022-08-16  9:44 Maxime Ripard
2022-07-29  9:45 Maxime Ripard
2022-07-21  8:55 Maxime Ripard
2022-07-14  7:18 Maxime Ripard
2022-07-08  5:43 Maxime Ripard
2022-06-30  7:24 Maxime Ripard
2022-06-23  6:41 Maxime Ripard
2022-06-16  7:25 Maxime Ripard
2022-06-09 10:07 Maxime Ripard
2022-05-26  9:05 Maxime Ripard
2022-05-20  7:24 Maxime Ripard
2022-05-13  7:30 Maxime Ripard
2022-05-05 15:50 Maarten Lankhorst
2022-04-27  6:04 Maarten Lankhorst
2022-04-22  8:44 Maxime Ripard
2022-04-07 10:56 Maarten Lankhorst
2022-03-24  7:58 Thomas Zimmermann
2022-03-17 10:29 Thomas Zimmermann
2022-03-10 19:35 Thomas Zimmermann
2022-03-03 10:06 Thomas Zimmermann
2022-02-23 19:27 Thomas Zimmermann
2022-02-17 11:16 Thomas Zimmermann
2022-02-10  9:50 Thomas Zimmermann
2022-02-03 11:29 Thomas Zimmermann
2022-01-27  9:04 Thomas Zimmermann
2022-01-14 12:54 Maxime Ripard
2021-12-16  8:26 Maxime Ripard
2021-12-09 12:43 Maxime Ripard
2021-12-02  8:44 Maxime Ripard
2021-11-25 10:18 Maxime Ripard
2021-11-18  7:54 Maxime Ripard
2021-11-11  8:48 Thomas Zimmermann
2021-10-28  7:23 Maxime Ripard
2021-10-26 12:17 Maarten Lankhorst
2021-10-21  9:33 Maarten Lankhorst
2021-10-14 12:19 Maarten Lankhorst
2021-10-15  5:17 ` Dave Airlie
2021-10-06  9:21 Maarten Lankhorst
2021-09-30 10:06 Maarten Lankhorst
2021-10-01  9:50 ` Daniel Vetter
2021-10-01 14:46   ` Daniel Vetter
2021-09-08 17:44 Thomas Zimmermann
2021-09-09  3:35 ` Dave Airlie
2021-09-09  9:30   ` Daniel Vetter
2021-09-10  6:20     ` Dave Airlie
2021-08-18 19:18 Thomas Zimmermann
2021-08-12  8:29 Thomas Zimmermann
2021-08-04 18:09 Thomas Zimmermann
2021-07-28 12:52 Thomas Zimmermann
2021-07-22 11:50 Thomas Zimmermann
2021-07-15  8:32 Thomas Zimmermann
2021-06-24 19:03 Maxime Ripard
2021-06-10 17:16 Maxime Ripard
2021-06-03  8:53 Maxime Ripard
2021-05-27 12:08 Maxime Ripard
2021-05-20 14:08 Maxime Ripard
2021-05-13 13:36 Maxime Ripard
2021-04-09  8:23 Maarten Lankhorst
2021-03-25 11:43 Maarten Lankhorst
2021-03-18 11:33 Maarten Lankhorst
2021-03-18 12:31 ` Daniel Vetter
2021-03-18 15:51   ` Maarten Lankhorst
2021-03-11 10:49 Maarten Lankhorst
2021-02-24 10:27 Thomas Zimmermann
2021-02-25  1:55 ` Dave Airlie
2021-02-25  7:53   ` Thomas Zimmermann
2021-02-25  8:29     ` Maxime Ripard
2021-02-25  8:54     ` Daniel Vetter
2021-02-10 14:08 Thomas Zimmermann
2021-02-02 12:36 Thomas Zimmermann
2021-01-27  7:56 Thomas Zimmermann
2021-01-27  8:13 ` Thomas Zimmermann
2021-01-20 12:09 Thomas Zimmermann
2021-01-20 12:14 ` Thomas Zimmermann
2021-01-12 13:21 Thomas Zimmermann
2021-01-08  9:34 Thomas Zimmermann
2021-01-08  9:53 ` Daniel Vetter
2020-12-03 12:59 Maxime Ripard
2020-11-26  8:54 Maxime Ripard
2020-11-19  8:39 Maxime Ripard
2020-11-12 13:07 Maxime Ripard
2020-11-05 10:13 Maxime Ripard
2020-10-29 17:34 Maxime Ripard
2020-10-01  7:21 Maarten Lankhorst
2020-09-24 10:47 Maarten Lankhorst
2020-09-18 11:11 Maarten Lankhorst
2020-09-10  5:51 Maarten Lankhorst
2020-08-26  7:40 Maarten Lankhorst
2020-08-12 13:24 Maarten Lankhorst
2020-08-04 12:55 Thomas Zimmermann
2020-07-28 11:04 Thomas Zimmermann
2020-07-22  7:03 Thomas Zimmermann
2020-07-15 17:17 Thomas Zimmermann
2020-07-08 12:10 Thomas Zimmermann
2020-07-02  7:51 Thomas Zimmermann
2020-06-25  8:27 Thomas Zimmermann
2020-05-28 11:09 Maxime Ripard
2020-05-14  7:35 Maxime Ripard
2020-05-07 16:01 Maxime Ripard
2020-04-30 15:32 Maxime Ripard
2020-04-23 10:32 Maxime Ripard
2020-03-26 14:04 Maarten Lankhorst
2020-03-18 14:07 Maarten Lankhorst
2020-03-18 11:55 Maarten Lankhorst
2020-03-05 10:19 Maarten Lankhorst
2020-02-20 10:06 Maarten Lankhorst
2020-02-07  9:13 Maarten Lankhorst
2020-01-22 21:37 Sean Paul
2020-01-16 16:28 Sean Paul
2020-01-08 20:59 Sean Paul
2019-12-31 15:25 Sean Paul
2019-12-11 21:21 Sean Paul
2019-11-25  9:43 Maxime Ripard
2019-11-25  9:43 ` Maxime Ripard
2019-11-13 14:26 Maxime Ripard
2019-11-13 14:26 ` Maxime Ripard
2019-11-07  8:22 Maxime Ripard
2019-11-07  8:22 ` Maxime Ripard
2019-10-30 18:22 Maxime Ripard
2019-10-30 18:22 ` Maxime Ripard
2019-10-23 11:26 Maxime Ripard
2019-10-23 11:26 ` Maxime Ripard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YO2Ywqla3CgS+AbL@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.