[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yid31AK5BlZEgmoA@google.com>
Date: Tue, 8 Mar 2022 15:35:48 +0000
From: Lee Jones <lee.jones@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Alim Akhtar <alim.akhtar@...sung.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linus.walleij@...aro.org,
robh+dt@...nel.org, krzysztof.kozlowski@...onical.com,
linux-samsung-soc@...r.kernel.org, pankaj.dubey@...sung.com,
andi@...zian.org, linux-spi@...r.kernel.org, linux-fsd@...la.com,
'Adithya K V' <adithya.kv@...sung.com>
Subject: Re: [RESEND PATCH v3 1/2] spi: dt-bindings: samsung: Add fsd spi
compatible
On Tue, 08 Mar 2022, Mark Brown wrote:
> 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.
Right.
Which patch(es) contain the dependencies please Alim?
I tend to send out pull-requests for cross-subsystem changes I merge.
Not sure I see anything relevant in my tree currently.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists