From: Nathan Chancellor <nathan@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Rostislav Krasny <rostiprodev@gmail.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/1] kconfig: move XPM icons to separate files
Date: Fri, 19 Dec 2025 13:39:32 -0700 [thread overview]
Message-ID: <176617677285.1406915.9246716063376321712.b4-ty@kernel.org> (raw)
In-Reply-To: <20251217015409.30102-1-rostiprodev@gmail.com>
On Wed, 17 Dec 2025 03:54:08 +0200, Rostislav Krasny wrote:
> On Wed, 17 Dec 2025 at 00:39, Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > Yes, "make xconfig" worked properly before applying this patch.
> >
> > .qconf.cmd (generated by build) tells me I am using Qt6.
> > I don't see any build errors/warnings.
> >
> > qt-core-devel & qt-base-common-devel are v6.10.1-1.2 from
> > openSUSE Tumbleweed.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next
Thanks!
[1/1] kconfig: move XPM icons to separate files
https://git.kernel.org/kbuild/c/18e2d526bf245
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted.
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
prev parent reply other threads:[~2025-12-19 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 14:09 [PATCH v2 0/1] kconfig: move XPM icons to separate files Rostislav Krasny
2025-12-13 14:09 ` [PATCH v2 1/1] " Rostislav Krasny
2025-12-16 7:10 ` Randy Dunlap
2025-12-16 20:38 ` Rostislav Krasny
2025-12-16 22:39 ` Randy Dunlap
2025-12-17 1:54 ` [PATCH v3 0/1] " Rostislav Krasny
2025-12-17 1:54 ` [PATCH v3 1/1] " Rostislav Krasny
2025-12-17 2:02 ` Randy Dunlap
2025-12-17 2:06 ` [PATCH v3 0/1] " Randy Dunlap
2025-12-19 20:39 ` Nathan Chancellor [this message]
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=176617677285.1406915.9246716063376321712.b4-ty@kernel.org \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nsc@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostiprodev@gmail.com \
/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