linux-kernel - Re: [PATCH v5 2/2] pinctrl: qcom: Add glymur pinctrl driver

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <bd533089-586c-431c-a548-4f0f6132dc7c@kernel.org>
Date: Wed, 3 Sep 2025 12:09:53 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Pankaj Patil <pankaj.patil@....qualcomm.com>, linus.walleij@...aro.org
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 rajendra.nayak@....qualcomm.com, linux-arm-msm@...r.kernel.org,
 linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 2/2] pinctrl: qcom: Add glymur pinctrl driver

On 03/09/2025 11:53, Pankaj Patil wrote:
>>> +module_exit(glymur_tlmm_exit);
>>> +
>>> +MODULE_DESCRIPTION("QTI GLYMUR TLMM driver");
>>> +MODULE_LICENSE("GPL");
>>> +MODULE_DEVICE_TABLE(of, glymur_tlmm_of_match);
>>> -- 
>>> 2.34.1
>>>
> This patch was not pulled in linux-next,
> commit- 9a1d01fbf43f56a02026eee44181f70108a0dec8
> Does this need a rebase?
> 

Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content. Pasting ENTIRE unreleated patch, 2000
(!!!) lines just to say something at the bottom.

Do you see anyone applied it? No. So it cannot appear in linux-next.

Best regards,
Krzysztof