From: Mark Brown <broonie@kernel.org> To: Alim Akhtar <alim.akhtar@samsung.com> Cc: 'Lee Jones' <lee.jones@linaro.org>, 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 15:01:57 +0000 [thread overview] Message-ID: <Yidv5aGB3CljCEWg@sirena.org.uk> (raw) In-Reply-To: <010901d832fb$212124f0$63636ed0$@samsung.com> [-- Attachment #1: Type: text/plain, Size: 830 bytes --] On Tue, Mar 08, 2022 at 08:15:15PM +0530, Alim Akhtar wrote: > >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. I need the changes that are hard dependencies to actually be in my tree so my tree is not broken, -next isn't good enough here. If there are dependencies for things you're posting you should explicitly say what they are when you post (not just vauge statements that there are dependencies), and when you post things that will be dependencies for other trees it's good to mention this so that people can think about putting them on a separate branch for easier cross merging. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Alim Akhtar <alim.akhtar@samsung.com> Cc: 'Lee Jones' <lee.jones@linaro.org>, 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 15:01:57 +0000 [thread overview] Message-ID: <Yidv5aGB3CljCEWg@sirena.org.uk> (raw) In-Reply-To: <010901d832fb$212124f0$63636ed0$@samsung.com> [-- Attachment #1.1: Type: text/plain, Size: 830 bytes --] On Tue, Mar 08, 2022 at 08:15:15PM +0530, Alim Akhtar wrote: > >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. I need the changes that are hard dependencies to actually be in my tree so my tree is not broken, -next isn't good enough here. If there are dependencies for things you're posting you should explicitly say what they are when you post (not just vauge statements that there are dependencies), and when you post things that will be dependencies for other trees it's good to mention this so that people can think about putting them on a separate branch for easier cross merging. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 176 bytes --] _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-08 15:02 UTC|newest] Thread overview: 22+ 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 2022-03-08 12:16 ` 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 12:16 ` 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:24 ` Mark Brown 2022-03-08 13:58 ` Lee Jones 2022-03-08 13:58 ` Lee Jones 2022-03-08 14:31 ` Mark Brown 2022-03-08 14:31 ` Mark Brown 2022-03-08 14:45 ` Alim Akhtar 2022-03-08 14:45 ` Alim Akhtar 2022-03-08 15:01 ` Mark Brown [this message] 2022-03-08 15:01 ` Mark Brown 2022-03-08 15:35 ` Lee Jones 2022-03-08 15:35 ` Lee Jones 2022-03-08 16:22 ` Alim Akhtar 2022-03-08 16:22 ` Alim Akhtar 2022-03-08 16:19 ` Alim Akhtar 2022-03-08 16:19 ` Alim Akhtar 2022-03-08 20:09 ` Mark Brown 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=Yidv5aGB3CljCEWg@sirena.org.uk \ --to=broonie@kernel.org \ --cc=adithya.kv@samsung.com \ --cc=alim.akhtar@samsung.com \ --cc=andi@etezian.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.