From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Markus Elfring <Markus.Elfring@web.de>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] drm/loongson: Introduce component framework support
Date: Thu, 25 Jul 2024 04:13:44 +0800 [thread overview]
Message-ID: <3013c48e-1757-4e43-a0c0-d2b3af9f3100@linux.dev> (raw)
In-Reply-To: <b3f75c6c-6c3e-41ee-92b9-ac5d9cca53f8@web.de>
Hi,
On 7/24/24 15:30, Markus Elfring wrote:
>> In some display subsystems, the functionality of a PCIe device may too
>
> might be?
>
>
> …
>> of the dirver is loaded, …
>
> driver?
>
>
> …
>> its dependencies ready before it can register the service to userspace.
>
> user space?
>
>
> …
>> submodule by creating platform devices manually during driverload time.
>
> driver load?
>
>
> …
>> device as a DRM proxy, which will attach the common drm routines to our
>
> DRM?
>
>
> …
>> While at it, also do some cleanups.
>
> I find such information suspicious.
> Is there any need to offer adjustments as separate update steps?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10#n81
Thanks a lot for review, I will try to fix those problems in the future.
> Regards,
> Markus
next prev parent reply other threads:[~2024-07-24 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 18:34 [PATCH v4 0/1] drm/loongson: Introduce component framework support Sui Jingfeng
2024-07-23 18:34 ` [PATCH v4 1/1] " Sui Jingfeng
2024-07-24 7:30 ` [PATCH v4] " Markus Elfring
2024-07-24 20:13 ` Sui Jingfeng [this message]
2024-07-23 19:47 ` [PATCH v4 0/1] " Markus Elfring
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=3013c48e-1757-4e43-a0c0-d2b3af9f3100@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=Markus.Elfring@web.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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