From: "Danilo Krummrich" <dakr@kernel.org>
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<broonie@kernel.org>, <will@kernel.org>,
<grygorii.strashko@ti.com>, <ssantosh@kernel.org>,
<khilman@kernel.org>, <linusw@kernel.org>, <brgl@kernel.org>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio: omap: do not register driver in probe()
Date: Tue, 27 Jan 2026 14:37:55 +0100 [thread overview]
Message-ID: <DFZEVBSZTGK8.2227V5O5GQS9T@kernel.org> (raw)
In-Reply-To: <176950495232.13307.15142034347404555496.b4-ty@oss.qualcomm.com>
On Tue Jan 27, 2026 at 10:09 AM CET, Bartosz Golaszewski wrote:
> Applied, thanks!
>
> [1/1] gpio: omap: do not register driver in probe()
> commit: 3cb53b083fa665ec14c52962f50b9c1df48cf87b
I think you missed to pick up the diff in [1]. Please let me know if you want a
fixup patch for this.
(One unrelated note, just be because I noticed by accident. Your applied patches
seem to use https://lore.kernel.org for Link: tags, while it has been agreed to
use https://patch.msgid.link instead [2].
I just mention it since it might be unintentional, i.e. it might be that your
tooling does not consider it.
Personally, I use b4 and have the following in my .gitconfig:
[b4]
linkmask = https://patch.msgid.link/%s
Not sure this is still necessary in the latest version though.)
[1] https://lore.kernel.org/all/DFW0SC4QG4W8.C7BRHX02W3IK@kernel.org/
[2] https://lore.kernel.org/all/CAHk-=wj5MATvT-FR8qNpXuuBGiJdjY1kRfhtzuyBSpTKR+=Vtw@mail.gmail.com/
next prev parent reply other threads:[~2026-01-27 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 13:31 [PATCH] gpio: omap: do not register driver in probe() Danilo Krummrich
2026-01-23 13:44 ` Danilo Krummrich
2026-01-26 9:06 ` Bartosz Golaszewski
2026-01-26 11:35 ` Danilo Krummrich
2026-01-23 13:57 ` Danilo Krummrich
2026-01-23 14:19 ` Greg KH
2026-01-23 14:25 ` Danilo Krummrich
2026-01-23 15:23 ` Greg KH
2026-01-23 15:48 ` Danilo Krummrich
2026-01-27 9:09 ` Bartosz Golaszewski
2026-01-27 13:37 ` Danilo Krummrich [this message]
2026-01-27 19:26 ` Bartosz Golaszewski
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=DFZEVBSZTGK8.2227V5O5GQS9T@kernel.org \
--to=dakr@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=khilman@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ssantosh@kernel.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.