From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/3] Fix some error handling paths in 'meson_drv_bind_master()'
Date: Tue, 13 Mar 2018 10:40:26 +0100 [thread overview]
Message-ID: <d0bc2518-ec6d-d919-f358-579211c50d9a@baylibre.com> (raw)
In-Reply-To: <cover.1520885192.git.christophe.jaillet@wanadoo.fr>
On 12/03/2018 21:15, Christophe JAILLET wrote:
> 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(-)
>
Hi,
Thanks for the fixes, since they are not critical, I pushed them on drm-misc-next, they will be backported onto stable tree by the stable team later on using the Fixes tag.
Neil
prev parent reply other threads:[~2018-03-13 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 20:15 Christophe JAILLET
2018-03-12 20:15 ` [PATCH 1/3] drm/meson: Fix an un-handled error path " 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 ` Neil Armstrong [this message]
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=d0bc2518-ec6d-d919-f358-579211c50d9a@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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: 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
all inboxes | Powered by JetHome®