On 25/09/2019 23:51, Adam Ford wrote:
Has anyone debugged why the hang is happening?
I started to debug this, but I got distracted when I noticed the LCD
did't work at all on modern kernels. I have that fixed now, so I can
go back to investigating this.
Working version:
[7.999359] DISPC:
https://bugs.freedesktop.org/show_bug.cgi?id=111819
--- Comment #5 from Dennis Schridde ---
Created attachment 145523
--> https://bugs.freedesktop.org/attachment.cgi?id=145523&action=edit
emerge --info mesa libdrm llvm linux-firmware xorg-server
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=111819
Dennis Schridde changed:
What|Removed |Added
Attachment #145521|cpuinfo.log |/proc/cpuinfo
description|
https://bugs.freedesktop.org/show_bug.cgi?id=111819
--- Comment #4 from Dennis Schridde ---
Created attachment 145522
--> https://bugs.freedesktop.org/attachment.cgi?id=145522&action=edit
lshw
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=111819
--- Comment #3 from Dennis Schridde ---
Created attachment 145521
--> https://bugs.freedesktop.org/attachment.cgi?id=145521&action=edit
cpuinfo.log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=111819
--- Comment #2 from Dennis Schridde ---
Created attachment 145520
--> https://bugs.freedesktop.org/attachment.cgi?id=145520&action=edit
glxinfo
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=111819
Bug ID: 111819
Summary: When starting Signal or Steam via Flatpak: [gfxhub]
retry page fault (src_id:0 ring:0 vmid:1 pasid:32770,
for process X pid 2148 thread X:cs0 pid 2151) in page
https://bugs.freedesktop.org/show_bug.cgi?id=111819
--- Comment #1 from Dennis Schridde ---
Created attachment 145519
--> https://bugs.freedesktop.org/attachment.cgi?id=145519&action=edit
lspci -vv
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111659
--- Comment #4 from Brad Campbell ---
Previous oops (Same oops with v5.3.1) was triggered by changing the audio
volume. I assume something to do with the volume OSD tickles the GPU.
--
You are receiving this mail because:
You are the assignee
On 2019/9/25 下午9:21, Michael S. Tsirkin wrote:
On Wed, Sep 25, 2019 at 08:45:21PM +0800, Jason Wang wrote:
On 2019/9/25 下午5:09, Tian, Kevin wrote:
From: Jason Wang [mailto:jasow...@redhat.com]
Sent: Tuesday, September 24, 2019 9:54 PM
This patch implements basic support for mdev driver that s
https://bugs.freedesktop.org/show_bug.cgi?id=111659
--- Comment #3 from Brad Campbell ---
Created attachment 145517
--> https://bugs.freedesktop.org/attachment.cgi?id=145517&action=edit
Same oops with v5.3.1
Same oops, newer kernel.
--
You are receiving this mail because:
You are the assigne
On Mon, Sep 23, 2019 at 01:59:25AM +, Lowry Li (Arm Technology China) wrote:
> From: "Lowry Li (Arm Technology China)"
>
> Adds system power management support in KMS kernel driver.
>
> Depends on:
> https://patchwork.freedesktop.org/series/62377/
>
> Changes since v1:
> Since we have unifi
https://bugs.freedesktop.org/show_bug.cgi?id=111811
--- Comment #2 from Daniel Drake ---
This is an ACPI reduced hardware platform, S3 suspend is not available.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mai
From: Gustavo Padovan
Add implementation for async plane update callbacks
Signed-off-by: Gustavo Padovan
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Tina Zhang
Signed-off-by: Helen Koike
Tested-by: Tina Zhang
---
Hi,
I ran the following tests and no regressions were found:
./scr
From: Gustavo Padovan
Replace the legacy cursor implementation by the async callbacks
Signed-off-by: Gustavo Padovan
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Helen Koike
---
Changes in v11: None
Changes in v10: None
Changes in v9:
- v8: https://patchwork.kernel.org/patch/108433
> From: Jason Wang
> Sent: Wednesday, September 25, 2019 8:45 PM
>
>
> On 2019/9/25 下午5:09, Tian, Kevin wrote:
> >> From: Jason Wang [mailto:jasow...@redhat.com]
> >> Sent: Tuesday, September 24, 2019 9:54 PM
> >>
> >> This patch implements basic support for mdev driver that supports
> >> virtio
https://bugs.freedesktop.org/show_bug.cgi?id=98271
John changed:
What|Removed |Added
Status|RESOLVED|CLOSED
Resolution|MOVED
Reviewed-by: Lyude Paul
Cc: Mikita Lipski - figured you'd want to know ahead of time you'll need to
update your changes to drm_dp_calc_pbn_mode() to match
On Wed, 2019-09-25 at 17:14 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Get rid of the drm_fixp_from_fraction() usage and just do
Reviewed-by: Lyude Paul
On Wed, 2019-09-25 at 17:14 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Make drm_dp_get_vc_payload() tolerate arbitrary DP_LINK_BW_*
> values, just like drm_dp_bw_code_to_link_rate() does since commit
> 57a1b0893782 ("drm: Make the bw/link rate calculations mor
Add a DT node for the DisplayPort subsystem, a hard IP present in the
Zynq Ultrascale+ MPSoC.
Signed-off-by: Laurent Pinchart
---
arch/arm64/boot/dts/xilinx/zynqmp-clk.dtsi | 4
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 21 +
2 files changed, 25 insertions(+)
diff -
From: Hyun Kwon
The bindings describe the ZynqMP DP subsystem. They don't support the
interface with the programmable logic (FPGA) or audio yet.
Signed-off-by: Hyun Kwon
Signed-off-by: Laurent Pinchart
---
Changes since v8:
- Convert to yaml
- Rename aclk to dp_apb_clk
---
.../display/xlnx/x
Enable the dpsub device and wire it up to the PS-GTR PHY lanes routed to
the DisplayPort connector.
Signed-off-by: Laurent Pinchart
---
.../arm64/boot/dts/xilinx/zynqmp-zcu106-revA.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-zcu106-
Hello,
Here's a new version of the Xilinx ZynqMP DisplayPort Subsystem driver.
I've taken over v8 of the series ([1]) from Hyun and addressed all the
review comments I had posted, plus quite a few additional issues (Daniel
mentioned in a private conversation that this should teach me to be less
pi
This inits the panel orientation property for the mediatek dsi driver
if the panel orientation (connector.display_info.panel_orientation) is
not DRM_MODE_PANEL_ORIENTATION_UNKNOWN.
Signed-off-by: Derek Basehore
Acked-by: Sam Ravnborg
Reviewed-by: CK Hu
---
drivers/gpu/drm/mediatek/mtk_dsi.c |
This adds a helper function for reading the rotation (panel
orientation) from the device tree.
Signed-off-by: Derek Basehore
Reviewed-by: Sam Ravnborg
---
drivers/gpu/drm/drm_panel.c | 43 +
include/drm/drm_panel.h | 9
2 files changed, 52 inser
Not every platform needs quirk detection for panel orientation, so
split the drm_connector_init_panel_orientation_property into two
functions. One for platforms without the need for quirks, and the
other for platforms that need quirks.
Signed-off-by: Derek Basehore
Acked-by: Sam Ravnborg
---
dr
Devicetree systems can set panel orientation via a panel binding, but
there's no way, as is, to propagate this setting to the connector,
where the property need to be added.
To address this, this patch sets orientation, as well as other fixed
values for the panel, in the drm_panel_attach function.
This adds the plumbing for reading panel rotation from the devicetree
and sets up adding a panel property for the panel orientation on
Mediatek SoCs when a rotation is present.
v8 changes:
-added reviewed-by tags
-fixed conflict with i915 patch that recently landed
-Added additional documentation
UGH this is entirely my fault, sorry about that. This reference got left in
when I cherry-picked this patch from a different series.
Reviewed-by: Lyude Paul
Feel free to push right away
On Wed, 2019-09-25 at 15:46 -0700, Matt Roper wrote:
> It looks like one of the topology manager mutexes may
It looks like one of the topology manager mutexes may have been renamed
during a rebase, but the destruction function wasn't updated with the
new name:
error: ‘struct drm_dp_mst_topology_mgr’ has no member named
‘delayed_destroy_lock’
Fixes: 50094b5dcd32 ("drm/dp_mst: Destroy topology_mgr m
Since we're going to be reprobing the entire topology state on resume
now using sideband transactions, we need to ensure that we actually have
short HPD irqs enabled before calling drm_dp_mst_topology_mgr_resume().
So, do that.
Changes since v4:
* Fix typo in comments
Cc: Juston Li
Cc: Imre Deak
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #88 from jeroenimo ---
Found this thread while googling the error from the log.
AMD Ryzen 3600
Asrock B350 motherboard
ASrock RX560 Radeon GPU
Ubuntu and Xubuntu 18.04 and 19.04 both lockups so not useable, after login
almost imm
Hi Dave, Daniel,
More fixes for 5.4. Nothing major.
The following changes since commit e16a7cbced7110866dcde84e504909ea85099bbd:
drm/amdgpu: flag navi12 and 14 as experimental for 5.4 (2019-09-18 08:29:30
-0500)
are available in the Git repository at:
git://people.freedesktop.org/~agd5f/
On Wed, Sep 25, 2019 at 11:52 AM Robin Murphy wrote:
>
> On 25/09/2019 17:16, Rob Herring wrote:
> > On Wed, Sep 25, 2019 at 10:30 AM Nicolas Saenz Julienne
> > wrote:
> >>
> >> On Wed, 2019-09-25 at 16:09 +0100, Robin Murphy wrote:
> >>> On 25/09/2019 15:52, Nicolas Saenz Julienne wrote:
>
On 5/28/19 4:11 AM, Tomi Valkeinen wrote:
> Hi,
>
> On 10/05/2019 22:42, Adam Ford wrote:
>> Currently the source code is compiled using hard-coded values
>> from CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK. This patch allows this
>> clock divider value to be moved to the device tree and be changed
>> witho
On Wed, 2019-09-25 at 16:00 -0400, Sean Paul wrote:
> On Tue, Sep 03, 2019 at 04:45:58PM -0400, Lyude Paul wrote:
> > Yes-you read that right. Currently there is literally no locking in
> > place for any of the drm_dp_mst_port struct members that can be modified
> > in response to a link address re
On Wed, 2019-09-25 at 15:27 -0400, Sean Paul wrote:
> On Tue, Sep 03, 2019 at 04:45:54PM -0400, Lyude Paul wrote:
> > Since we're going to be implementing suspend/resume reprobing very soon,
> > we need to make sure we are extra careful to ensure that our locking
> > actually protects the topology
On Tue, May 28, 2019 at 10:53 AM Tomi Valkeinen wrote:
>
> Hi,
>
> On 28/05/2019 18:09, Adam Ford wrote:
> > On Tue, May 28, 2019 at 4:11 AM Tomi Valkeinen
> > wrote:
> >>
> >> Hi,
> >>
> >> On 10/05/2019 22:42, Adam Ford wrote:
> >>> Currently the source code is compiled using hard-coded values
https://bugs.freedesktop.org/show_bug.cgi?id=111792
--- Comment #14 from Sylvain BERTRAND ---
I seems I should stay on amd-staging-drm-next then.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-d
On 9/25/19 12:07 PM, Andrey Grodzovsky wrote:
> On 9/25/19 12:00 PM, Steven Price wrote:
>
>> On 25/09/2019 16:56, Grodzovsky, Andrey wrote:
>>> On 9/25/19 11:14 AM, Steven Price wrote:
>>>
drm_sched_cleanup_jobs() attempts to free finished jobs, however
because
it is called as the
On Wed, 2019-09-25 at 14:16 -0400, Sean Paul wrote:
> On Tue, Sep 03, 2019 at 04:45:41PM -0400, Lyude Paul wrote:
> > When reprobing an MST topology during resume, we have to account for the
> > fact that while we were suspended it's possible that mstbs may have been
> > removed from any ports in t
On Tue, Sep 03, 2019 at 04:46:02PM -0400, Lyude Paul wrote:
> Since we're going to be reprobing the entire topology state on resume
> now using sideband transactions, we need to ensure that we actually have
> short HPD irqs enabled before calling drm_dp_mst_topology_mgr_resume().
> So, do that.
>
On Tue, Sep 03, 2019 at 04:46:00PM -0400, Lyude Paul wrote:
> In order for suspend/resume reprobing to work, we need to be able to
> perform sideband communications during suspend/resume, along with
> runtime PM suspend/resume. In order to do so, we also need to make sure
> that nouveau doesn't bot
On Tue, Sep 03, 2019 at 04:45:59PM -0400, Lyude Paul wrote:
> This probably hasn't caused any problems up until now since it's
> probably nearly impossible to encounter this in the wild, however if we
> were to receive a connection status notification from the MST hub after
> resume while we're in
On Tue, Sep 03, 2019 at 04:45:58PM -0400, Lyude Paul wrote:
> Yes-you read that right. Currently there is literally no locking in
> place for any of the drm_dp_mst_port struct members that can be modified
> in response to a link address response, or a connection status response.
> Which literally m
https://bugs.freedesktop.org/show_bug.cgi?id=111792
--- Comment #13 from Alex Deucher ---
(In reply to Sylvain BERTRAND from comment #12)
> What are the differences then?
for my git repo:
- amd-staging-drm-next is our internal integration branch.
- drm-next is all of our new code for the next ke
On Tue, Sep 03, 2019 at 04:45:57PM -0400, Lyude Paul wrote:
> Once upon a time, hotplugging devices on MST branches actually worked in
> DRM. Now, it only works in amdgpu (likely because of how it's hotplug
> handlers are implemented). On both i915 and nouveau, hotplug
> notifications from MST bran
https://bugs.freedesktop.org/show_bug.cgi?id=111792
--- Comment #12 from Sylvain BERTRAND ---
What are the differences then?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedeskto
On Tue, Sep 03, 2019 at 04:45:56PM -0400, Lyude Paul wrote:
> These are most certainly accessed from far more than the mgr work. In
> fact, up_req_recv is -only- ever accessed from outside the mgr work.
>
> Cc: Juston Li
> Cc: Imre Deak
> Cc: Ville Syrjälä
> Cc: Harry Wentland
> Cc: Daniel Vet
From: Kevin Hilman
On some SoCs, the VPU is in a power-domain and needs runtime PM
enabled and used in order to keep the power domain on.
Signed-off-by: Kevin Hilman
---
drivers/gpu/drm/meson/meson_drv.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/meson/meson_drv.c
On Tue, Sep 03, 2019 at 04:45:55PM -0400, Lyude Paul wrote:
> The names for these functions are rather confusing. drm_dp_add_port()
> sounds like a function that would simply create a port and add it to a
> topology, and do nothing more. Similarly, drm_dp_update_port() would be
> assumed to be the
On Tue, Sep 03, 2019 at 04:45:54PM -0400, Lyude Paul wrote:
> Since we're going to be implementing suspend/resume reprobing very soon,
> we need to make sure we are extra careful to ensure that our locking
> actually protects the topology state where we expect it to. Turns out
> this isn't the case
On Tue, Sep 03, 2019 at 04:45:52PM -0400, Lyude Paul wrote:
> Turns out we've been forgetting for a while now to actually destroy any
> of the mutexes that we create in drm_dp_mst_topology_mgr. So, let's do
> that.
>
> Cc: Juston Li
> Cc: Imre Deak
> Cc: Ville Syrjälä
> Cc: Harry Wentland
> Cc
Reviewed-by: Lyude Paul
On Wed, 2019-09-25 at 17:14 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Replace the nested ifs with a single if and a logical AND.
>
> Cc: Lyude Paul
> Signed-off-by: Ville Syrjälä
> ---
> drivers/gpu/drm/drm_dp_mst_topology.c | 10 +-
> 1 file chan
https://bugs.freedesktop.org/show_bug.cgi?id=111761
--- Comment #7 from Alex Deucher ---
Does this patch help?
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-next-fixes&id=e0f32f78e51b9989ee89f608fd0dd10e9c230652
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111761
--- Comment #6 from Christian Zigotzky ---
With which good and bad commit should I start bisecting?
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mail
On Tue, Sep 03, 2019 at 04:45:46PM -0400, Lyude Paul wrote:
> This will allow us to add some locking for port->* members, in
> particular the PDT and ->connector, which can't be done from
> drm_dp_destroy_port() since we don't know what locks the caller might be
> holding.
Might be nice to mention
https://bugs.freedesktop.org/show_bug.cgi?id=111791
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111802
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111669
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111813
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111784
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111591
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111622
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111806
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111372
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111527
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111332
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111236
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111077
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=11
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110786
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110850
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110719
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111235
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110813
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111076
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110637
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110635
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110639
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110658
GitLab Migration User changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110713
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110711
GitLab Migration User changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110614
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110575
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110509
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110370
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110472
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109608
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110140
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109763
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109382
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109794
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109783
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110130
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109466
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110137
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109370
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|REOPEN
https://bugs.freedesktop.org/show_bug.cgi?id=109793
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109297
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
1 - 100 of 378 matches
Mail list logo
