From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com>, Dave Airlie <airlied@redhat.com>, Francisco Jerez <currojerez@riseup.net>, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] drm: encoder_slave: some updates Date: Mon, 16 Mar 2020 17:39:05 +0100 [thread overview] Message-ID: <20200316163907.13709-1-wsa+renesas@sang-engineering.com> (raw) While converting I2C users to new APIs, I found a refcounting problem in the encoder_slave implementation. This series fixes it and converts to the new API. Based on linux-next and only build tested. Wolfram Sang (2): drm: encoder_slave: fix refcouting error for modules drm: encoder_slave: use new I2C API drivers/gpu/drm/drm_encoder_slave.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: dri-devel@lists.freedesktop.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com> Subject: [PATCH 0/2] drm: encoder_slave: some updates Date: Mon, 16 Mar 2020 17:39:05 +0100 [thread overview] Message-ID: <20200316163907.13709-1-wsa+renesas@sang-engineering.com> (raw) While converting I2C users to new APIs, I found a refcounting problem in the encoder_slave implementation. This series fixes it and converts to the new API. Based on linux-next and only build tested. Wolfram Sang (2): drm: encoder_slave: fix refcouting error for modules drm: encoder_slave: use new I2C API drivers/gpu/drm/drm_encoder_slave.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) -- 2.20.1 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-03-16 16:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-16 16:39 Wolfram Sang [this message] 2020-03-16 16:39 ` [PATCH 0/2] drm: encoder_slave: some updates Wolfram Sang 2020-03-16 16:39 ` [PATCH 1/2] drm: encoder_slave: fix refcouting error for modules Wolfram Sang 2020-03-16 16:39 ` Wolfram Sang 2020-03-16 16:39 ` [PATCH 2/2] drm: encoder_slave: use new I2C API Wolfram Sang 2020-03-16 16:39 ` Wolfram Sang 2020-05-12 16:28 ` [PATCH 0/2] drm: encoder_slave: some updates Wolfram Sang 2020-05-12 16:28 ` Wolfram Sang 2020-05-13 9:35 ` Emil Velikov 2020-05-13 9:35 ` Emil Velikov 2020-05-17 20:50 ` Emil Velikov 2020-05-17 20:50 ` Emil Velikov
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=20200316163907.13709-1-wsa+renesas@sang-engineering.com \ --to=wsa+renesas@sang-engineering.com \ --cc=airlied@redhat.com \ --cc=currojerez@riseup.net \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ /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: linkBe 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.