From: Mark Brown <broonie@kernel.org>
To: Alim Akhtar <alim.akhtar@samsung.com>
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
Subject: Re: [PATCH v3 0/3] Add FSD SPI support
Date: Tue, 25 Jan 2022 13:54:36 +0000 [thread overview]
Message-ID: <YfABHDjdTgxytcUY@sirena.org.uk> (raw)
In-Reply-To: <20220125031604.76009-1-alim.akhtar@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
On Tue, Jan 25, 2022 at 08:46:01AM +0530, Alim Akhtar wrote:
> Note: This series is depended on [1] patches which adds
> support of FSD SoC and on Krzysztof's v6 [2] of spi schema changes
>
> [1] https://lkml.org/lkml/2022/1/24/583
> [2] https://lkml.org/lkml/2022/1/24/120
Please resend this when it can be applied, either wait until the
dependencies are in place or rebase on top of current code. In general
only build time dependencies matter here, the SoC support being merged
shouldn't be an issue one way or another.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-25 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220125032811epcas5p3ef7b2f4e4906c1da8ccb4a0b3ed9a591@epcas5p3.samsung.com>
2022-01-25 3:16 ` Alim Akhtar
[not found] ` <CGME20220125032821epcas5p128c99ca3654fce0ec046943c90211849@epcas5p1.samsung.com>
2022-01-25 3:16 ` [PATCH v3 1/3] spi: dt-bindings: samsung: Add fsd spi compatible Alim Akhtar
2022-01-28 0:26 ` Linus Walleij
2022-02-07 20:42 ` Rob Herring
[not found] ` <CGME20220125032825epcas5p2c5cf48a773fd26e089b31b0f6ddde83f@epcas5p2.samsung.com>
2022-01-25 3:16 ` [PATCH v3 2/3] spi: s3c64xx: Add spi port configuration for Tesla FSD SoC Alim Akhtar
2022-01-28 0:28 ` Linus Walleij
[not found] ` <CGME20220125032828epcas5p22fbacf42ebfb1b78c1f74f48d37aa381@epcas5p2.samsung.com>
2022-01-25 3:16 ` [PATCH v3 3/3] arm64: dts: fsd: Add SPI device nodes Alim Akhtar
2022-01-29 11:29 ` (subset) " Krzysztof Kozlowski
2022-01-25 13:54 ` Mark Brown [this message]
2022-03-08 12:11 ` [PATCH v3 0/3] Add FSD SPI support Alim Akhtar
2022-03-08 20:09 ` (subset) " 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=YfABHDjdTgxytcUY@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andi@etezian.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@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=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
all inboxes | Powered by JetHome®