From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Mark Brown'" <broonie@kernel.org>,
"'Lee Jones'" <lee.jones@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linus.walleij@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski@canonical.com>,
<linux-samsung-soc@vger.kernel.org>, <pankaj.dubey@samsung.com>,
<andi@etezian.org>, <linux-spi@vger.kernel.org>,
<linux-fsd@tesla.com>, "'Adithya K V'" <adithya.kv@samsung.com>
Subject: RE: [RESEND PATCH v3 1/2] spi: dt-bindings: samsung: Add fsd spi compatible
Date: Tue, 8 Mar 2022 20:15:15 +0530 [thread overview]
Message-ID: <010901d832fb$212124f0$63636ed0$@samsung.com> (raw)
In-Reply-To: <YidosChLIwIAKDmG@sirena.org.uk>
>-----Original Message-----
>From: Mark Brown [mailto:broonie@kernel.org]
>Sent: Tuesday, March 8, 2022 8:01 PM
>To: Lee Jones <lee.jones@linaro.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;
>krzysztof.kozlowski@canonical.com; linux-samsung-soc@vger.kernel.org;
>pankaj.dubey@samsung.com; andi@etezian.org; linux-spi@vger.kernel.org;
>linux-fsd@tesla.com; Adithya K V <adithya.kv@samsung.com>
>Subject: Re: [RESEND PATCH v3 1/2] spi: dt-bindings: samsung: Add fsd spi
>compatible
>
>On Tue, Mar 08, 2022 at 01:58:03PM +0000, Lee Jones wrote:
>> On Tue, 08 Mar 2022, Mark Brown wrote:
>
>> > I either need a pull request for the MFD changes or to wait until
>> > those changes have come in via Linus' tree.
>
>> You mean this one:
>
>> https://lore.kernel.org/all/YiYC7eYx2SpPILyl@google.com/
>
>> spi: dt-bindings: samsung: Convert to dtschema
>
>> Or something else?
>
>There were changes adding the FSD SoC as well as DT stuff IIRC.
FSD SoC DT changes are already in -next.
I think this can go with MFD tree because of immutable
branch between MFD, SPI and DT due for the v5.18 merge windows.
I am not sure if there are better ways to handle this.
Regards,
Alim
next prev parent reply other threads:[~2022-03-08 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220308120701epcas5p3d3d2f5c01055e8c1721ae0ec6c2aa681@epcas5p3.samsung.com>
2022-03-08 12:16 ` [RESEND PATCH v3 1/2] spi: dt-bindings: samsung: Add fsd spi compatible Alim Akhtar
[not found] ` <CGME20220308120705epcas5p21f5cf07d2ab98f89cf87fe3b9fd595b2@epcas5p2.samsung.com>
2022-03-08 12:16 ` [RESEND PATCH v3 2/2] spi: s3c64xx: Add spi port configuration for Tesla FSD SoC Alim Akhtar
2022-03-08 13:24 ` [RESEND PATCH v3 1/2] spi: dt-bindings: samsung: Add fsd spi compatible Mark Brown
2022-03-08 13:58 ` Lee Jones
2022-03-08 14:31 ` Mark Brown
2022-03-08 14:45 ` Alim Akhtar [this message]
2022-03-08 15:01 ` Mark Brown
2022-03-08 15:35 ` Lee Jones
2022-03-08 16:22 ` Alim Akhtar
2022-03-08 16:19 ` Alim Akhtar
2022-03-08 20:09 ` 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='010901d832fb$212124f0$63636ed0$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=adithya.kv@samsung.com \
--cc=andi@etezian.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lee.jones@linaro.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).