From: Thomas Zimmermann <tzimmermann@suse.de>
To: Jani Nikula <jani.nikula@linux.intel.com>,
mripard@kernel.org, maarten.lankhorst@linux.intel.com,
airlied@linux.ie, daniel@ffwll.ch
Cc: nouveau@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-tegra@vger.kernel.org,
freedreno@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Nouveau] [PATCH v2 3/5] drm/dp: Move DisplayPort helpers into separate helper module
Date: Wed, 15 Dec 2021 12:12:24 +0100 [thread overview]
Message-ID: <2165cfb8-c9c6-1aca-b492-587a8e07eb9f@suse.de> (raw)
In-Reply-To: <87pmpy3za7.fsf@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]
Hi
Am 15.12.21 um 12:04 schrieb Jani Nikula:
> On Wed, 15 Dec 2021, Thomas Zimmermann <tzimmermann@suse.de> wrote:
>> * move DP helper code into dp/ (Jani)
>
> I suggested adding the subdirectory, but I'm going to bikeshed the name,
> which I didn't suggest.
>
> $ find drivers/gpu/drm -mindepth 1 -maxdepth 1 -type d | wc -l
> 68
>
> Assuming we move more of the drm modules to subdirectories, how are they
> going to stand out from drivers?
>
> I suggested drm_dp, which I understand results in tautology, but hey,
> all the filenames under drm/ also have drm_*.[ch]. And I find that very
> useful for git greps and other code archeology. With just the dp name,
> you'd have to know and list all the drm subdirectories when looking up
> stuff that's part of drm but not drivers.
I think we have enough filename prefixes already. drm/drm_dp/drm_dp_ is
just ridiculous.
Best regards
Thomas
>
>
> BR,
> Jani.
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-12-15 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:43 [Nouveau] [PATCH v2 0/5] drm/dp: Move DisplayPort helpers into own module Thomas Zimmermann
2021-12-15 10:43 ` [Nouveau] [PATCH v2 1/5] drm/dp_mst: Remove trailing whitespace Thomas Zimmermann
2021-12-15 10:43 ` [Nouveau] [PATCH v2 2/5] drm/dp: Move DP declarations into separate header file Thomas Zimmermann
2021-12-15 10:43 ` [Nouveau] [PATCH v2 3/5] drm/dp: Move DisplayPort helpers into separate helper module Thomas Zimmermann
2021-12-15 11:04 ` Jani Nikula
2021-12-15 11:12 ` Thomas Zimmermann [this message]
2022-01-11 10:21 ` Javier Martinez Canillas
2022-01-08 23:56 ` Michał Mirosław
2022-01-11 18:58 ` Lyude Paul
2021-12-15 10:43 ` [Nouveau] [PATCH v2 4/5] drm/dp: Move public DisplayPort headers into dp/ Thomas Zimmermann
2021-12-15 10:43 ` [Nouveau] [PATCH v2 5/5] drm/dp: Move DisplayPort AUX bus helpers " Thomas Zimmermann
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=2165cfb8-c9c6-1aca-b492-587a8e07eb9f@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).