[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15fcb91a5214438fb69535bcf2df576e@EXMBX068.cuchost.com>
Date: Tue, 6 Dec 2022 08:32:38 +0000
From: JiaJie Ho <jiajie.ho@...rfivetech.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Rob Herring <robh@...nel.org>
CC: "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"Rob Herring" <robh+dt@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>
Subject: RE: [PATCH 5/6] dt-bindings: crypto: Add bindings for Starfive crypto
driver
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> Sent: Tuesday, December 6, 2022 4:26 PM
> To: JiaJie Ho <jiajie.ho@...rfivetech.com>; Rob Herring <robh@...nel.org>
> Cc: linux-crypto@...r.kernel.org; linux-riscv@...ts.infradead.org; Rob
> Herring <robh+dt@...nel.org>; Herbert Xu
> <herbert@...dor.apana.org.au>; Krzysztof Kozlowski
> <krzysztof.kozlowski+dt@...aro.org>; linux-kernel@...r.kernel.org;
> devicetree@...r.kernel.org; David S . Miller <davem@...emloft.net>
> Subject: Re: [PATCH 5/6] dt-bindings: crypto: Add bindings for Starfive crypto
> driver
>
> On 06/12/2022 04:48, JiaJie Ho wrote:
> >
> >
> > The #include in example have dependencies on the following patches:
> > https://patchwork.kernel.org/project/linux-riscv/cover/20221118010627.
> > 70576-1-hal.feng@...rfivetech.com/
> > https://patchwork.kernel.org/project/linux-riscv/cover/20221118011714.
> > 70877-1-hal.feng@...rfivetech.com/
> > I've noted them in the cover letter.
> > How do I add them in this patch?
>
> You cannot. Testing bot does not take dependencies, so it did not have
> above clock IDs. This also should point your attention that if crypto
> maintainers pick up this patch, they also won't have the clock IDs so their tree
> will have such failure as well.
>
> You can wait with your patch till dependency hits mainline or you can just
> replace clock IDs with numbers and drop the header (and later you can
> correct the example if needed... or leave it as is).
>
I'll replace the IDs and drop the header then.
Thanks.
Regards,
Jia Jie
Powered by blists - more mailing lists