dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Huang Rui <ray.huang@amd.com>
To: Dan Moulding <dmoulding@me.com>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"jason@jlekstrand.net" <jason@jlekstrand.net>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 0/1] Fix DRM driver initialization failure in kernel v5.14
Date: Mon, 16 Aug 2021 14:20:18 +0800	[thread overview]
Message-ID: <20210816062018.GB1179183@hr-amd> (raw)
In-Reply-To: <20210813165014.31106-1-dmoulding@me.com>

On Sat, Aug 14, 2021 at 12:50:14AM +0800, Dan Moulding wrote:
> Just a friendly reminder that this fix for a regression needs
> review. It should be a quick review.
> 
> It would probably be good to ensure this gets in before the final 5.14
> release, otherwise this is going to be a very visible regression for
> anyone that uses DRM and does not use debugfs.
> 

Just took a look at your patch, it's ok for me. Alex/Christian, could you
help to apply this fix if you have no concern?

Best Regards,
Ray

  reply	other threads:[~2021-08-16  6:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 19:59 [PATCH 0/1] Fix DRM driver initialization failure in kernel v5.14 Dan Moulding
2021-08-10 19:59 ` [PATCH 1/1] drm: ttm: Don't bail from ttm_global_init if debugfs_create_dir fails Dan Moulding
2021-08-11  9:27   ` Huacai Chen
2021-08-16  6:06   ` Huang Rui
2021-08-16  7:40   ` Christian König
2021-08-16 14:28     ` Jason Ekstrand
2021-08-13 16:50 ` [PATCH 0/1] Fix DRM driver initialization failure in kernel v5.14 Dan Moulding
2021-08-16  6:20   ` Huang Rui [this message]
2021-08-16 12:12     ` Christian König

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=20210816062018.GB1179183@hr-amd \
    --to=ray.huang@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=dmoulding@me.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jason@jlekstrand.net \
    /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;
as well as URLs for NNTP newsgroup(s).