From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Kevin Tang <kevin3.tang@gmail.com>,
mripard@kernel.org, sean@poorly.run, airlied@linux.ie,
daniel@ffwll.ch, robh+dt@kernel.org, mark.rutland@arm.com
Cc: orsonzhai@gmail.com, zhang.lyra@gmail.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, pony1.wu@gmail.com
Subject: Re: [PATCH v8 0/6] Add Unisoc's drm kms module
Date: Mon, 20 Dec 2021 16:03:24 +0100 [thread overview]
Message-ID: <4de5b255-4f2d-870e-a7f2-05f5c0069cfe@linux.intel.com> (raw)
In-Reply-To: <CAFPSGXaC1rMF+KLttBJvKzN=UxtFtRR1gO3L4cqdgPJu_jtQ_A@mail.gmail.com>
On 20-12-2021 14:55, Kevin Tang wrote:
> Dear Maarten,
> I see it from the cgit.freedesktop.org, our sprd drivers seems has
> been merged into drm-misc.
>
> Now, what shall we do next?
>
> BR,
> Best wishes
>
> Kevin Tang <kevin3.tang@gmail.com> 于2021年12月7日周二 22:27写道：
You should apply for commit rights to drm-misc, so you can maintain it.
https://drm.pages.freedesktop.org/maintainer-tools/commit-access.html
~Maarten
prev parent reply other threads:[~2021-12-20 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 14:27 Kevin Tang
2021-12-07 14:27 ` [PATCH v8 1/6] dt-bindings: display: add Unisoc's drm master bindings Kevin Tang
2021-12-07 14:27 ` [PATCH v8 2/6] drm/sprd: add Unisoc's drm kms master Kevin Tang
2021-12-07 14:27 ` [PATCH v8 3/6] dt-bindings: display: add Unisoc's dpu bindings Kevin Tang
2021-12-07 14:27 ` [PATCH v8 4/6] drm/sprd: add Unisoc's drm display controller driver Kevin Tang
2021-12-07 14:27 ` [PATCH v8 5/6] dt-bindings: display: add Unisoc's mipi dsi controller bindings Kevin Tang
2021-12-07 14:27 ` [PATCH v8 6/6] drm/sprd: add Unisoc's drm mipi dsi&dphy driver Kevin Tang
2021-12-10 11:44 ` Maarten Lankhorst
2021-12-20 13:55 ` [PATCH v8 0/6] Add Unisoc's drm kms module Kevin Tang
2021-12-20 15:03 ` Maarten Lankhorst [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=4de5b255-4f2d-870e-a7f2-05f5c0069cfe@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevin3.tang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=orsonzhai@gmail.com \
--cc=pony1.wu@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®