From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>, linus.walleij@linaro.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
rajendra.nayak@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] pinctrl: qcom: Add glymur pinctrl driver
Date: Wed, 3 Sep 2025 12:09:53 +0200 [thread overview]
Message-ID: <bd533089-586c-431c-a548-4f0f6132dc7c@kernel.org> (raw)
In-Reply-To: <9be4695b-54eb-461a-9e59-81670089ff38@oss.qualcomm.com>
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
next prev parent reply other threads:[~2025-09-03 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 6:55 [PATCH v5 0/2] pinctrl: qcom: Introduce Pinctrl for Glymur Pankaj Patil
2025-08-13 6:55 ` [PATCH v5 1/2] dt-bindings: pinctrl: qcom: Add Glymur pinctrl bindings Pankaj Patil
2025-09-03 10:08 ` Krzysztof Kozlowski
2025-09-03 11:01 ` Dmitry Baryshkov
2025-09-03 11:28 ` Krzysztof Kozlowski
2025-09-03 12:22 ` Dmitry Baryshkov
2025-09-04 12:59 ` Pankaj Patil
2025-08-13 6:55 ` [PATCH v5 2/2] pinctrl: qcom: Add glymur pinctrl driver Pankaj Patil
2025-08-13 10:14 ` Konrad Dybcio
2025-08-13 14:34 ` Bjorn Andersson
2025-09-03 9:53 ` Pankaj Patil
2025-09-03 10:09 ` Krzysztof Kozlowski [this message]
2025-09-04 19:34 ` Linus Walleij
2025-08-13 7:31 ` [PATCH v5 0/2] pinctrl: qcom: Introduce Pinctrl for Glymur Krzysztof Kozlowski
2025-08-13 9:48 ` Pankaj Patil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd533089-586c-431c-a548-4f0f6132dc7c@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=rajendra.nayak@oss.qualcomm.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).