From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
mbenes@suse.cz, x86@kernel.org
Subject: Re: drivers/gpu/drm/i915/i915.prelink.o: warning: objtool: __intel_wait_for_register_fw.cold()+0xce: relocation to !ENDBR: vlv_allow_gt_wake.cold+0x0
Date: Wed, 6 Apr 2022 15:44:13 -0300 [thread overview]
Message-ID: <Yk3ffdJ6a3Q2uWRG@kernel.org> (raw)
In-Reply-To: <20220405212032.3d858b31@gandalf.local.home>
Em Tue, Apr 05, 2022 at 09:20:32PM -0400, Steven Rostedt escreveu:
> On Wed, 06 Apr 2022 02:46:22 +0200
> Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > This covers the trace_printk() case which uses do_trace_printk(), but
> > the same problem exists in trace_puts() and ftrace_vprintk()...., no?
>
> Hmm, I'm not even sure why ftrace_vprintk() is there. It seems redundant.
>
> Arnaldo,
>
> Was there a reason for it. The commit that added it isn't very descriptive.
Yeah, I was young and in a hurry.
- Arnaldo
> commit 9011262a37cb438f0fa9394b5e83840db8f9680a
> Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> Date: Fri Jan 23 12:06:23 2009 -0200
>
> ftrace: add ftrace_vprintk
>
> Impact: new helper function
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> -- Steve
--
- Arnaldo
next prev parent reply other threads:[~2022-04-06 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 4:33 drivers/gpu/drm/i915/i915.prelink.o: warning: objtool: __intel_wait_for_register_fw.cold()+0xce: relocation to !ENDBR: vlv_allow_gt_wake.cold+0x0 kernel test robot
2022-04-05 14:01 ` Peter Zijlstra
2022-04-06 0:05 ` Josh Poimboeuf
2022-04-06 0:46 ` Thomas Gleixner
2022-04-06 1:20 ` Steven Rostedt
2022-04-06 18:44 ` Arnaldo Carvalho de Melo [this message]
2022-04-06 5:32 ` Josh Poimboeuf
2022-04-06 7:29 ` Peter Zijlstra
2022-04-06 14:19 ` Steven Rostedt
2022-04-06 7:43 ` Peter Zijlstra
2022-04-06 16:37 ` Josh Poimboeuf
2022-04-07 9:24 ` Peter Zijlstra
2022-04-06 14:14 ` Steven Rostedt
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=Yk3ffdJ6a3Q2uWRG@kernel.org \
--to=acme@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@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).