From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
krzysztof.kozlowski+dt@linaro.org, broonie@kernel.org
Cc: robh+dt@kernel.org, conor+dt@kernel.org, alim.akhtar@samsung.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, andre.draszik@linaro.org,
peter.griffin@linaro.org, semen.protsenko@linaro.org,
kernel-team@android.com, willmcvicker@google.com
Subject: Re: [PATCH 0/7] ARM: dts: samsung: specify the SPI fifosize
Date: Thu, 1 Feb 2024 11:33:18 +0100 [thread overview]
Message-ID: <85856b38-e42e-412b-b201-ee2798722f67@linaro.org> (raw)
In-Reply-To: <20240125151630.753318-1-tudor.ambarus@linaro.org>
On 25/01/2024 16:16, Tudor Ambarus wrote:
> Hi,
>
> The "samsung,spi-fifosize" was introduced in the following patch set:
> https://lore.kernel.org/linux-arm-kernel/20240125145007.748295-1-tudor.ambarus@linaro.org/T/#t
>
Judging by Rob's statement the bindings were not accepted, so I drop
this series for now.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-02-01 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:16 [PATCH 0/7] ARM: dts: samsung: specify the SPI fifosize Tudor Ambarus
2024-01-25 15:16 ` [PATCH 1/7] ARM: dts: samsung: s5pv210: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 2/7] ARM: dts: samsung: exynos3250: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 3/7] ARM: dts: samsung: exynos4: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 4/7] ARM: dts: samsung: exynos5250: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 5/7] ARM: dts: samsung: exynos5450: " Tudor Ambarus
2024-01-30 17:08 ` Henrik Grimler
2024-01-25 15:16 ` [PATCH 6/7] ARM: dts: samsung: exynos5433: " Tudor Ambarus
2024-01-25 15:16 ` [PATCH 7/7] ARM: dts: samsung: exynosautov9: " Tudor Ambarus
2024-01-25 15:53 ` [PATCH 0/7] ARM: dts: samsung: " Mark Brown
2024-01-25 15:56 ` Krzysztof Kozlowski
2024-02-01 10:33 ` Krzysztof Kozlowski [this message]
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=85856b38-e42e-412b-b201-ee2798722f67@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).