All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	airlied@redhat.com, daniel@ffwll.ch, john.p.donnelly@oracle.com
Subject: Re: [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd'
Date: Thu, 28 Nov 2019 14:23:36 +0000	[thread overview]
Message-ID: <20191128142337.1B32A217F5@mail.kernel.org> (raw)
In-Reply-To: <20191126101529.20356-4-tzimmermann@suse.de>

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin").

The bot has tested the following trees: v5.3.13.

v5.3.13: Build failed! Errors:
    drivers/gpu/drm/mgag200/mgag200_drv.c:104:18: error: ‘drm_vram_mm_debugfs_init’ undeclared here (not in a function); did you mean ‘drm_client_debugfs_init’?


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@redhat.com, daniel@ffwll.ch, john.p.donnelly@oracle.com,
Cc: , stable@vger.kernel.org,
	Neil Armstrong <narmstrong@baylibre.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Gerd Hoffmann <kraxel@redhat.com>,
	José Roberto de Souza <jose.souza@intel.com>,
	Dave Airlie <airlied@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd'
Date: Thu, 28 Nov 2019 14:23:36 +0000	[thread overview]
Message-ID: <20191128142337.1B32A217F5@mail.kernel.org> (raw)
Message-ID: <20191128142336.qCQfbdpZ9d69J89OVwJbEpNyLyggNMk4ELf5xJvUWXA@z> (raw)
In-Reply-To: <20191126101529.20356-4-tzimmermann@suse.de>

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin").

The bot has tested the following trees: v5.3.13.

v5.3.13: Build failed! Errors:
    drivers/gpu/drm/mgag200/mgag200_drv.c:104:18: error: ‘drm_vram_mm_debugfs_init’ undeclared here (not in a function); did you mean ‘drm_client_debugfs_init’?


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-11-28 14:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 10:15 [PATCH v2 0/3] drm/mgag200: Workaround HW bug with non-0 offset Thomas Zimmermann
2019-11-26 10:15 ` [PATCH v2 1/3] drm/mgag200: Extract device type from flags Thomas Zimmermann
2019-11-26 10:15   ` Thomas Zimmermann
2019-11-27 16:29   ` Emil Velikov
2019-11-27 16:29     ` Emil Velikov
2019-11-27 18:08     ` Thomas Zimmermann
2019-11-27 18:08       ` Thomas Zimmermann
2019-11-28 12:46       ` Emil Velikov
2019-11-28 12:46         ` Emil Velikov
2019-11-26 10:15 ` [PATCH v2 2/3] drm/mgag200: Store flags from PCI driver data in device structure Thomas Zimmermann
2019-11-26 10:15   ` Thomas Zimmermann
2019-11-28 14:23   ` Sasha Levin
2019-11-28 14:23     ` Sasha Levin
2019-11-26 10:15 ` [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd' Thomas Zimmermann
2019-11-26 10:15   ` Thomas Zimmermann
2019-11-28 14:23   ` Sasha Levin [this message]
2019-11-28 14:23     ` Sasha Levin
2019-12-03 17:30     ` FAILED - " John Donnelly
2019-12-03 17:30       ` John Donnelly
2019-12-06  0:48       ` John Donnelly
2019-12-06  0:48         ` John Donnelly
2019-12-06  6:02         ` Thomas Zimmermann
2019-12-06  6:02           ` Thomas Zimmermann

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=20191128142337.1B32A217F5@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=airlied@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=john.p.donnelly@oracle.com \
    --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.