All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Bobroff <sbobroff@linux.ibm.com>
To: daniel@ffwll.ch, airlied@redhat.com, airlied@linux.ie,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Two AST driver fixes
Date: Mon,  3 Dec 2018 11:53:19 +1100	[thread overview]
Message-ID: <cover.1543798395.git.sbobroff@linux.ibm.com> (raw)

Hello,

Here are two (attempted) fixes for the AST DRM driver. The issues they fix are
both seen when the ast driver is unloaded (tested on Power9, although it looks
like the second one is architecture independent).

I'm fairly confident about the first fix, as it looks pretty straight forward.

The second seems reasonable, but I don't know this area of the kernel very well.

Cheers,
Sam.

Patch set changelog follows:

Patch set v2: 
Patch 1/2: drm/ast: Fix incorrect free on ioregs
Patch 2/2: drm/ast: Fix connector leak during driver unload
* Changed to use drm_crtc_force_disable_all().

Patch set v1:
Patch 1/2: drm/ast: Fix incorrect free on ioregs
Patch 2/2: drm/ast: Fix connector leak during driver unload

Sam Bobroff (2):
  drm/ast: Fix incorrect free on ioregs
  drm/ast: Fix connector leak during driver unload

 drivers/gpu/drm/ast/ast_fb.c   | 1 +
 drivers/gpu/drm/ast/ast_main.c | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

-- 
2.19.0.2.gcad72f5712

             reply	other threads:[~2018-12-03  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  0:53 Sam Bobroff [this message]
2018-12-03  0:53 ` [PATCH v2 1/2] drm/ast: Fix incorrect free on ioregs Sam Bobroff
2018-12-03  0:53 ` [PATCH v2 2/2] drm/ast: Fix connector leak during driver unload Sam Bobroff
2018-12-04 12:13   ` Daniel Vetter
2018-12-04 12:13     ` Daniel Vetter

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.1543798395.git.sbobroff@linux.ibm.com \
    --to=sbobroff@linux.ibm.com \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@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: link
Be 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.