From: Nathan Chancellor <nathan@kernel.org>
To: Luca Leonardo Scorcia <l.scorcia@gmail.com>
Cc: Daniel Lezcano <daniel.lezcano@kernel.org>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: vmlinux.o: warning: objtool: mtk_timer_probe+0x23: no-cfi indirect call!
Date: Thu, 29 Oct 2026 21:42:53 -0700 [thread overview]
Message-ID: <20261030044253.GA2699480@ax162> (raw)
In-Reply-To: <CAORyz2KEJ5M86-+z2zWXVTJwbNO8SY4DWjn5Y6EO_-nPhdiytw@mail.gmail.com>
On Thu, Oct 29, 2026 at 07:54:10PM +0100, Luca Leonardo Scorcia wrote:
> Being a new contributor I'm not quite sure what the process is now -
> should I send out a patch with the correction, just as I did for the
> initial contribution? Or is it going to be fixed by the maintainers
> autonomously? (Obviously adding a Suggested-by tag with the rest of
> the bots' tags).
Since the patch is already in Linus's tree, you'll need to send a follow
up fix. Not only is it good practice for learning how to follow up on
issues/feedback on your patches, it will help build trust with
maintainers in case you submit other patches in the future because you
have already shown you are willing to take ownership of them. It is
generally better to send a patch if you are able than relying on a
maintainer to handle it, not only because they don't typically have the
bandwidth but because you will get full credit for the fix.
Thanks for taking care of this!
--
Cheers,
Nathan
prev parent reply other threads:[~2026-10-30 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 19:10 vmlinux.o: warning: objtool: mtk_timer_probe+0x23: no-cfi indirect call! kernel test robot
2026-10-28 20:24 ` Nathan Chancellor
2026-10-29 18:54 ` Luca Leonardo Scorcia
2026-10-29 22:06 ` Daniel Lezcano
2026-10-30 4:42 ` 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=20261030044253.GA2699480@ax162 \
--to=nathan@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=l.scorcia@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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