From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: narmstrong@baylibre.com, airlied@linux.ie, carlo@caione.org,
khilman@baylibre.com
Cc: dri-devel@lists.freedesktop.org,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/3] Fix some error handling paths in 'meson_drv_bind_master()'
Date: Mon, 12 Mar 2018 20:15:07 +0000 [thread overview]
Message-ID: <cover.1520885192.git.christophe.jaillet@wanadoo.fr> (raw)
Patch 1 and 3 are fixes.
Patch 2 is just a kind of clean-up noticed while patching this driver.
If patch 2 is considered as useless, patch 3 can be applied on top of
patch 1, it does nor depend on the 2nd patch.
Christophe JAILLET (3):
drm/meson: Fix an un-handled error path in 'meson_drv_bind_master()'
drm/meson: Use drm_dev_put() instead of drm_dev_unref()
drm/meson: Fix some error handling paths in 'meson_drv_bind_master()'
drivers/gpu/drm/meson/meson_drv.c | 33 ++++++++++++++++++++++-----------
1 file changed, 22 insertions(+), 11 deletions(-)
--
2.14.1
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
next reply other threads:[~2018-03-12 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 20:15 Christophe JAILLET [this message]
2018-03-12 20:15 ` [PATCH 1/3] drm/meson: Fix an un-handled error path in 'meson_drv_bind_master()' Christophe JAILLET
2018-03-13 9:36 ` Neil Armstrong
2018-03-12 20:15 ` [PATCH 2/3] drm/meson: Use drm_dev_put() instead of drm_dev_unref() Christophe JAILLET
2018-03-13 9:34 ` Neil Armstrong
2018-03-12 20:15 ` [PATCH 3/3] drm/meson: Fix some error handling paths in 'meson_drv_bind_master()' Christophe JAILLET
2018-03-13 9:36 ` Neil Armstrong
2018-03-13 9:40 ` [PATCH 0/3] " Neil Armstrong
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=cover.1520885192.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=airlied@linux.ie \
--cc=carlo@caione.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox