All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Luca Leonardo Scorcia <l.scorcia@gmail.com>,
	Nathan Chancellor <nathan@kernel.org>
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 23:06:13 +0100	[thread overview]
Message-ID: <542fea3d-c587-4077-bc75-28afdf3e543d@oss.qualcomm.com> (raw)
In-Reply-To: <CAORyz2KEJ5M86-+z2zWXVTJwbNO8SY4DWjn5Y6EO_-nPhdiytw@mail.gmail.com>


Hi Luca,

On 10/29/26 19:54, Luca Leonardo Scorcia wrote:
> Thank you Nathan for the analysis and suggested fix. I agree your
> patch would be useful even if the warning wasn't there, to make the
> device probe more robust.
> 
> 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? 

If you can send a fix that would be nice

> Or is it going to be fixed by the maintainers
> autonomously? (Obviously adding a Suggested-by tag with the rest of
> the bots' tags).
> 
> Thank you for your help


  reply	other threads:[~2026-10-29 22:06 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 [this message]
2026-10-30  4:42     ` Nathan Chancellor

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=542fea3d-c587-4077-bc75-28afdf3e543d@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --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=nathan@kernel.org \
    --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 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.