From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <mripard@kernel.org>,
Samuel Holland <samuel@sholland.org>
Cc: Samuel Holland <samuel@sholland.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Jagan Teki <jagan@amarulasolutions.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH 3/4] drm/sun4i: dsi: Add a variant structure
Date: Sun, 14 Aug 2022 09:46:51 +0200 [thread overview]
Message-ID: <4731474.GXAFRqVoOG@jernej-laptop> (raw)
In-Reply-To: <20220812074257.58254-4-samuel@sholland.org>
Dne petek, 12. avgust 2022 ob 09:42:55 CEST je Samuel Holland napisal(a):
> Replace the ad-hoc calls to of_device_is_compatible() with a structure
> describing the differences between variants. This is in preparation for
> adding more variants to the driver.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
next prev parent reply other threads:[~2022-08-14 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 7:42 [PATCH 0/4] drm/sun4i: dsi: Support the A100/D1 controller variant Samuel Holland
2022-08-12 7:42 ` [PATCH 1/4] dt-bindings: display: sun6i-dsi: Fix clock conditional Samuel Holland
2022-08-12 10:48 ` Krzysztof Kozlowski
2022-08-12 7:42 ` [PATCH 2/4] dt-bindings: display: sun6i-dsi: Add the A100 variant Samuel Holland
2022-08-12 10:49 ` Krzysztof Kozlowski
2022-08-12 22:58 ` Samuel Holland
2022-08-16 10:15 ` Krzysztof Kozlowski
2022-08-12 7:42 ` [PATCH 3/4] drm/sun4i: dsi: Add a variant structure Samuel Holland
2022-08-14 7:46 ` Jernej Škrabec [this message]
2022-08-15 6:42 ` Maxime Ripard
2022-08-12 7:42 ` [PATCH 4/4] drm/sun4i: dsi: Add the A100 variant Samuel Holland
2022-08-14 7:47 ` Jernej Škrabec
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=4731474.GXAFRqVoOG@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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