linux-kernel - Re: [PATCH v7 0/3] PCI: tegra: Allow building as a module

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: <CALHNRZ8PZzseaTSCvhM6o7jMVYtVdHTczurXh1q+DY5MG62+DA@mail.gmail.com>
Date: Mon, 18 Aug 2025 13:39:48 -0500
From: Aaron Kling <webgeek1234@...il.com>
To: Manivannan Sadhasivam <mani@...nel.org>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>, Thomas Gleixner <tglx@...utronix.de>, 
	Lorenzo Pieralisi <lpieralisi@...nel.org>, Rob Herring <robh@...nel.org>, 
	Bjorn Helgaas <bhelgaas@...gle.com>, Thierry Reding <thierry.reding@...il.com>, 
	Jonathan Hunter <jonathanh@...dia.com>, "Rafael J. Wysocki" <rafael@...nel.org>, 
	Krzysztof Wilczyński <kwilczynski@...nel.org>, 
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, 
	linux-tegra@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v7 0/3] PCI: tegra: Allow building as a module

On Fri, Aug 1, 2025 at 1:01 AM Manivannan Sadhasivam <mani@...nel.org> wrote:
>
> On Thu, Jul 31, 2025 at 05:01:55PM GMT, Aaron Kling wrote:
> > On Thu, Jul 31, 2025 at 4:59 PM Aaron Kling via B4 Relay
> > <devnull+webgeek1234.gmail.com@...nel.org> wrote:
> > >
> > > Signed-off-by: Aaron Kling <webgeek1234@...il.com>
> > > ---
> > > Changes in v7:
> > > - Rebased on 6.16
> > > - Updated mailing address list
> > > - Link to v6: https://lore.kernel.org/r/20250507-pci-tegra-module-v6-0-5fe363eaa302@gmail.com
> > >
> > > Changes in v6:
> > > - Remove unused debugfs cleanup function, as caught by kernel ci
> > > - Link to v5: https://lore.kernel.org/r/20250505-pci-tegra-module-v5-0-827aaac998ba@gmail.com
> > >
> > > Changes in v5:
> > > - Copy commit message exactly word for word on patch 1, as required by reviewer
> > > - Delete remove callback in patch 3, per request
> > > - Don't clean up debugfs, per request, which drops patch 4 entirely
> > > - Link to v4: https://lore.kernel.org/r/20250505-pci-tegra-module-v4-0-088b552c4b1a@gmail.com
> > >
> > > Changes in v4:
> > > - Updated commit messages for patches 1 and 2, per review
> > > - Link to v3: https://lore.kernel.org/r/20250502-pci-tegra-module-v3-0-556a49732d70@gmail.com
> > >
> > > Changes in v3:
> > > - Add patch to drop remove callback, per request
> > > - Link to v2: https://lore.kernel.org/r/20250428-pci-tegra-module-v2-0-c11a4b912446@gmail.com
> > >
> > > Changes in v2:
> > > - Add patch to export tegra_cpuidle_pcie_irqs_in_use as required when
> > >   building pci-tegra as a module for arm
> > > - Drop module exit to prevent module unloading, as requested
> > > - Link to v1: https://lore.kernel.org/r/20250420-pci-tegra-module-v1-0-c0a1f831354a@gmail.com
> > >
> > > ---
> > > Aaron Kling (3):
> > >       irqdomain: Export irq_domain_free_irqs
> > >       cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use
> > >       PCI: tegra: Allow building as a module
> > >
> > >  drivers/cpuidle/cpuidle-tegra.c    |  1 +
> > >  drivers/pci/controller/Kconfig     |  2 +-
> > >  drivers/pci/controller/pci-tegra.c | 35 ++++-------------------------------
> > >  kernel/irq/irqdomain.c             |  1 +
> > >  4 files changed, 7 insertions(+), 32 deletions(-)
> > > ---
> > > base-commit: 038d61fd642278bab63ee8ef722c50d10ab01e8f
> > > change-id: 20250313-pci-tegra-module-7cbd1c5e70af
> > >
> > > Best regards,
> > > --
> > > Aaron Kling <webgeek1234@...il.com>
> > >
> > >
> >
> > Continuing the conversation from the last revision [0]. Is there any
> > path forward for this series?
> >
>
> Daniel, could you please look into the cpufreq patch?

Another two weeks with no response to a review request. And over two
months total since the cpuidle maintainers were initially asked to
look. Is there a policy for dealing with lack of responses?

Aaron