From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@canonical.com>,
"'Andi Shyti'" <andi@etezian.org>,
"'Mark Brown'" <broonie@kernel.org>,
"'Rob Herring'" <robh+dt@kernel.org>,
"'Pratyush Yadav'" <p.yadav@ti.com>, <linux-spi@vger.kernel.org>,
<linux-samsung-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: "'Sam Protsenko'" <semen.protsenko@linaro.org>,
"'Rob Herring'" <robh@kernel.org>
Subject: RE: [PATCH v3 4/4] spi: s3c64xx: allow controller-data to be optional
Date: Fri, 14 Jan 2022 14:57:49 +0900 [thread overview]
Message-ID: <00a601d8090b$a92da220$fb88e660$@samsung.com> (raw)
In-Reply-To: <20220112100046.68068-5-krzysztof.kozlowski@canonical.com>
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> Sent: Wednesday, January 12, 2022 7:01 PM
> To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>; Andi Shyti
> <andi@etezian.org>; Mark Brown <broonie@kernel.org>; Rob Herring
> <robh+dt@kernel.org>; Pratyush Yadav <p.yadav@ti.com>; linux-
> spi@vger.kernel.org; linux-samsung-soc@vger.kernel.org;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org
> Cc: Sam Protsenko <semen.protsenko@linaro.org>; Rob Herring
> <robh@kernel.org>
> Subject: [PATCH v3 4/4] spi: s3c64xx: allow controller-data to be optional
>
> The Samsung SoC SPI driver requires to provide controller-data node for
> each of SPI peripheral device nodes. Make this controller-data node
> optional, so DTS could be simpler.
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Reviewed-by: Chanho Park <chanho61.park@samsung.com>
next prev parent reply other threads:[~2022-01-14 5:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 10:00 [PATCH v3 0/4] spi: dt-bindings: samsung: convert to dtschema Krzysztof Kozlowski
2022-01-12 10:00 ` [PATCH v3 1/4] ARM: dts: exynos: split dmas into array of phandles in Exynos5250 Krzysztof Kozlowski
2022-01-16 15:28 ` Alim Akhtar
2022-01-12 10:00 ` [PATCH v3 2/4] spi: dt-bindings: samsung: convert to dtschema Krzysztof Kozlowski
2022-01-19 19:31 ` Pratyush Yadav
2022-01-19 19:49 ` Krzysztof Kozlowski
2022-01-20 7:06 ` Pratyush Yadav
2022-01-20 7:36 ` Krzysztof Kozlowski
2022-01-20 9:00 ` Pratyush Yadav
2022-01-20 9:24 ` Krzysztof Kozlowski
2022-01-20 10:08 ` Pratyush Yadav
2022-01-12 10:00 ` [PATCH v3 3/4] spi: dt-bindings: samsung: allow controller-data to be optional Krzysztof Kozlowski
2022-01-12 10:00 ` [PATCH v3 4/4] spi: s3c64xx: " Krzysztof Kozlowski
2022-01-14 5:57 ` Chanho Park [this message]
2022-01-14 16:13 ` Sam Protsenko
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='00a601d8090b$a92da220$fb88e660$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=andi@etezian.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=p.yadav@ti.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.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).