From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Andi Shyti <andi@etezian.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, robh+dt@kernel.org,
linux-samsung-soc@vger.kernel.org, pankaj.dubey@samsung.com,
broonie@kernel.org, linux-spi@vger.kernel.org,
linux-fsd@tesla.com, Adithya K V <adithya.kv@samsung.com>
Subject: Re: [PATCH v2 1/3] spi: dt-bindings: samsung: Add fsd spi compatible
Date: Sat, 22 Jan 2022 11:33:01 +0100 [thread overview]
Message-ID: <CA+Eumj7ab9E_4sbVPSQjOc-ZwM9LVdrgE=rj3duYKBYHjtDhyA@mail.gmail.com> (raw)
In-Reply-To: <YevcOlARxNcBeDJE@jack.zhora.eu>
On Sat, 22 Jan 2022 at 11:28, Andi Shyti <andi@etezian.org> wrote:
>
> Hi Krzysztof and Alim,
>
> On Fri, Jan 21, 2022 at 07:33:15PM +0100, Krzysztof Kozlowski wrote:
> > On 20/01/2022 20:24, Alim Akhtar wrote:
> > > Adds spi controller dt-binding compatible information for
> > > Tesla Full Self-Driving (FSD) SoC.
> > >
> > > Cc: linux-fsd@tesla.com
> > > Signed-off-by: Adithya K V <adithya.kv@samsung.com>
> > > Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
> > > ---
> > > Documentation/devicetree/bindings/spi/samsung,spi.yaml | 1 +
> > > 1 file changed, 1 insertion(+)
> >
> > I think you forgot to mention - in cover letter - that this depends on
> > my Samsung SPI bindings conversion to dtschema.
>
> It's written in the cover letter:
>
> "Note: This series is depended on [1] patches which adds
> support of FSD SoC and on Krzysztof's v5 [2] of spi schema
> changes"
Indeed, it is. I simply could not find the cover letter so I assumed
none was sent, but it just got hidden.
next prev parent reply other threads:[~2022-01-22 10:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220120193608epcas5p466c73dfdcc7eb5cdcd52516a635fca79@epcas5p4.samsung.com>
2022-01-20 19:24 ` [PATCH v2 0/3] Add FSD SPI support Alim Akhtar
[not found] ` <CGME20220120193613epcas5p238851849d212e01d7d830d78ca7d6379@epcas5p2.samsung.com>
2022-01-20 19:24 ` [PATCH v2 1/3] spi: dt-bindings: samsung: Add fsd spi compatible Alim Akhtar
2022-01-21 18:33 ` Krzysztof Kozlowski
2022-01-22 10:28 ` Andi Shyti
2022-01-22 10:33 ` Krzysztof Kozlowski [this message]
2022-01-21 18:34 ` Krzysztof Kozlowski
[not found] ` <CGME20220120193618epcas5p45be1db500363072e647bf179623f8e7a@epcas5p4.samsung.com>
2022-01-20 19:24 ` [PATCH v2 2/3] spi: s3c64xx: Add spi port configuration for Tesla FSD SoC Alim Akhtar
2022-01-21 18:33 ` Krzysztof Kozlowski
2022-01-22 10:32 ` Andi Shyti
[not found] ` <CGME20220120193622epcas5p3a65c8424c6a01aed9a87f5ac2a89eb06@epcas5p3.samsung.com>
2022-01-20 19:24 ` [PATCH v2 3/3] arm64: dts: fsd: Add SPI device nodes Alim Akhtar
2022-01-22 10:42 ` Andi Shyti
2022-01-24 17:00 ` Alim Akhtar
2022-03-08 20:09 ` (subset) [PATCH v2 0/3] Add FSD SPI support Mark Brown
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='CA+Eumj7ab9E_4sbVPSQjOc-ZwM9LVdrgE=rj3duYKBYHjtDhyA@mail.gmail.com' \
--to=krzysztof.kozlowski@canonical.com \
--cc=adithya.kv@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=andi@etezian.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.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).