linux-kernel - Re: [PATCH v4 1/4] ARM: dts: qcom: apq8064: Use generic node name for DMA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 26 Apr 2022 13:49:05 -0700
From:   Bjorn Andersson <bjorn.andersson@...aro.org>
To:     Kuldeep Singh <singh.kuldeep87k@...il.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Andy Gross <agross@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v4 1/4] ARM: dts: qcom: apq8064: Use generic node name
 for DMA

On Sat 23 Apr 11:09 PDT 2022, Kuldeep Singh wrote:

> On Sat, Apr 23, 2022 at 09:03:39AM -0700, Bjorn Andersson wrote:
> > On Thu 21 Apr 10:18 PDT 2022, Kuldeep Singh wrote:
> > 
> > > Qcom BAM DT spec expects generic DMA controller node name as
> > > "dma-controller" to enable validations.
> > > 
> > > Signed-off-by: Kuldeep Singh <singh.kuldeep87k@...il.com>
> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> > 
> > It seems that I picked up v3, but patchwork-bot didn't send out any
> > notifications.
> 
> Yes, somehow there was no notification for this series as well as geni
> uart/i2c patches also.
> 
> >
> > Please double check linux-next to confirm that we got them all sorted
> > out.
> 
> I checked dma dts patches[1] and they are in next/linux-next.
> I hope I checked the right tree, please correct me if it's wrong.
> 
> Please note, there was one small typo fix from v3->v4 in commit
> header(s/User/Use). Not sure if it's worth updating as it's already in
> next tree, upto you. Thanks!
> 

I generally never rebase my trees, as that's causing issues for anyone
references commits in my tree. So we'll have to live with this typo.

Thanks,
Bjorn