From: Shawn Guo <shawnguo@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: devicetree@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Jacopo Mondi <jacopo@jmondi.org>,
Eugen Hristev <eugen.hristev@microchip.com>,
Hugues Fruchet <hugues.fruchet@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v3 3/6] ARM: dts: freescale: Use new media bus type macros
Date: Wed, 25 Jan 2023 10:16:44 +0800 [thread overview]
Message-ID: <20230125021643.GA20713@T480> (raw)
In-Reply-To: <20220615221410.27459-4-laurent.pinchart@ideasonboard.com>
On Thu, Jun 16, 2022 at 01:14:07AM +0300, Laurent Pinchart wrote:
> Now that a header exists with macros for the media interface bus-type
> values, replace hardcoding numerical constants with the corresponding
> macros in the DT sources.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Applied, thanks!
next prev parent reply other threads:[~2023-01-25 2:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 22:14 [PATCH v3 0/6] dt-bindings: Add macros for video interface bus types Laurent Pinchart
2022-06-15 22:14 ` [PATCH v3 1/6] dt-bindings: media: " Laurent Pinchart
2022-06-27 22:14 ` Rob Herring
2022-06-28 10:46 ` Jacopo Mondi
2022-11-17 10:02 ` Paul Elder
2022-06-15 22:14 ` [PATCH v3 2/6] dt-bindings: Use new video interface bus type macros in examples Laurent Pinchart
2022-06-27 22:16 ` Rob Herring
2022-06-27 23:40 ` Laurent Pinchart
2022-07-16 9:28 ` Sakari Ailus
2022-07-16 15:12 ` Laurent Pinchart
2022-11-21 21:10 ` Sakari Ailus
2022-06-15 22:14 ` [PATCH v3 3/6] ARM: dts: freescale: Use new media bus type macros Laurent Pinchart
2023-01-14 15:30 ` Laurent Pinchart
2023-01-25 2:16 ` Shawn Guo [this message]
2022-06-15 22:14 ` [PATCH v3 4/6] ARM: dts: omap: " Laurent Pinchart
2023-01-14 15:37 ` Laurent Pinchart
2023-01-19 7:59 ` Tony Lindgren
2022-06-15 22:14 ` [PATCH v3 5/6] ARM: dts: renesas: " Laurent Pinchart
2022-11-18 9:27 ` Lad, Prabhakar
2023-01-14 15:26 ` Laurent Pinchart
2023-01-16 10:24 ` Geert Uytterhoeven
2023-01-16 10:38 ` Laurent Pinchart
2023-01-16 10:44 ` Geert Uytterhoeven
2023-01-16 10:49 ` Laurent Pinchart
2023-01-16 11:23 ` Geert Uytterhoeven
2022-06-15 22:14 ` [PATCH v3 6/6] ARM: dts: stm32: " Laurent Pinchart
2023-01-14 15:36 ` Laurent Pinchart
2023-01-17 10:44 ` Alexandre TORGUE
2023-01-17 11:24 ` Alexandre TORGUE
2022-07-17 6:54 ` [PATCH v3 0/6] dt-bindings: Add macros for video interface bus types Sakari Ailus
2022-11-18 9:23 ` Paul Elder
2022-11-19 19:15 ` Laurent Pinchart
2022-11-21 10:54 ` Sakari Ailus
2022-11-21 11:06 ` Laurent Pinchart
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=20230125021643.GA20713@T480 \
--to=shawnguo@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eugen.hristev@microchip.com \
--cc=festevam@gmail.com \
--cc=hugues.fruchet@foss.st.com \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).