From 9bf7cbc7f6fa528ee215b14341a173d995e52377 Mon Sep 17 00:00:00 2001 From: Roman Gilg Date: Sun, 25 Aug 2019 13:40:11 +0200 Subject: [PATCH] Remove change-set null check Summary: It is unnecessary to check if the change-set is null when looking at the KWayland code. Also the check would be useless at the moment anyway because before the check we access the change-set already in the DRM backend and at the check we would not return if it would be null. Test Plan: Relevant auto tests pass. Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D23428 --- abstract_wayland_output.cpp | 4 ---- 1 file changed, 4 deletions(-) diff --git a/abstract_wayland_output.cpp b/abstract_wayland_output.cpp index a156a9b926..b5f045fbf2 100644 --- a/abstract_wayland_output.cpp +++ b/abstract_wayland_output.cpp @@ -112,10 +112,6 @@ void AbstractWaylandOutput::setChanges(KWayland::Server::OutputChangeSet *change qCDebug(KWIN_CORE) << "Set changes in AbstractWaylandOutput."; Q_ASSERT(!m_waylandOutputDevice.isNull()); - if (!changes) { - qCDebug(KWIN_CORE) << "No changes."; - // No changes to an output is an entirely valid thing - } //enabledChanged is handled by plugin code if (changes->modeChanged()) { qCDebug(KWIN_CORE) << "Setting new mode:" << changes->mode();