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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqLukNhEM99y0TmC6c2G-c0tLYOC7RPQdD-6J0x-WRLYog@mail.gmail.com>
Date: Tue, 20 Jan 2026 12:48:26 -0600
From: Rob Herring <robh@...nel.org>
To: Jassi Brar <jassisinghbrar@...il.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Jingyi Wang <jingyi.wang@....qualcomm.com>, 
	Manivannan Sadhasivam <mani@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	aiqun.yu@....qualcomm.com, tingwei.zhang@....qualcomm.com, 
	trilok.soni@....qualcomm.com, yijie.yang@....qualcomm.com, 
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	devicetree@...r.kernel.org, Sibi Sankar <sibi.sankar@....qualcomm.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: mailbox: qcom: Add IPCC support for
 Kaanapali and Glymur Platforms

On Sun, Jan 18, 2026 at 12:37 PM Jassi Brar <jassisinghbrar@...il.com> wrote:
>
> On Fri, Jan 16, 2026 at 11:13 AM Rob Herring <robh@...nel.org> wrote:
> >
> > On Fri, Jan 16, 2026 at 10:25 AM Krzysztof Kozlowski <krzk@...nel.org> wrote:
> > >
> > > On 16/01/2026 17:20, Rob Herring wrote:
> > > > On Fri, Oct 31, 2025 at 12:41:44AM -0700, Jingyi Wang wrote:
> > > >> Document the Inter-Processor Communication Controller on the Qualcomm
> > > >> Kaanapali and Glymur Platforms, which will be used to route interrupts
> > > >> across various subsystems found on the SoC.
> > > >>
> > > >> Co-developed-by: Sibi Sankar <sibi.sankar@....qualcomm.com>
> > > >> Signed-off-by: Sibi Sankar <sibi.sankar@....qualcomm.com>
> > > >> Signed-off-by: Jingyi Wang <jingyi.wang@....qualcomm.com>
> > > >> ---
> > > >>  Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml | 2 ++
> > > >>  1 file changed, 2 insertions(+)
> > > >
> > > > I guess no one is going to apply this, so I did.
> > > >
> > > > If your patches don't get applied, please chase the maintainers (Jassi)
> > > > to apply them.
> > >
> > >
> > > This or it is an effect of known problem with mailbox and interconnect
> > > subsystems - maintainers never send notifications of applied patches
> > > (neither publicly nor privately like Greg does), so you will never know
> > > if anything gets applied.
> > >
> > > This as well could be in the next silently (wasn't in 15th Jan, though).
> >
> > Further investigation finds Jassi did apply this and 3 other patches.
> > Stephen reported a conflict on 1/6 with another Qcom patch
> > (conflicting with Bjorn's tree). No reply to Stephen, but *all* the
> > mbox binding patches were dropped.
> >
> > Here's what was dropped:
> >
> > f8f632c18c32 dt-bindings: mbox: add pic64gx mailbox compatibility to
> > mpfs mailbox
> > 945dc11a38a0 dt-bindings: mailbox: qcom: Add CPUCP mailbox controller
> > bindings for Kaanapali
> > 66b6e5daa915 dt-bindings: mailbox: qcom: Add IPCC support for
> > Kaanapali and Glymur Platforms
> > 9a92e22740e6 dt-bindings: mailbox: mediatek,mt8196-vcp-mbox: add mtk
> > vcp-mbox document
> >
> Yes, I had to reconstruct the mailbox for-next branch because some
> patch had an issue and the pr was not merged after a very late fix.
> Sorry I didn't realize people not receiving pick-confirmations was so
> problematic. I will make sure I reply to every patch that I pick.

TBC, the issue is not so much sending applied emails or not. It's the
not applying patches for 6 weeks (best I can tell, this patch was
never in next until after 12/10), and then dropping them silently.


Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ