From: kernel test robot <lkp@intel.com>
To: Fidal Palamparambil <rootuserhere@gmail.com>,
linux-modules@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
mcgrof@kernel.org, petr.pavlu@suse.com, da.gomez@kernel.org,
samitolvanen@google.com, linux-kernel@vger.kernel.org,
Fidal palamparambil <rootuserhere@gmail.com>
Subject: Re: [PATCH] Fixed the build warning in init_trace_printk_function_export():
Date: Mon, 8 Sep 2025 02:33:43 +0800 [thread overview]
Message-ID: <202509080203.SxCdQOOY-lkp@intel.com> (raw)
In-Reply-To: <20250907140755.529-1-rootuserhere@gmail.com>
Hi Fidal,
kernel test robot noticed the following build errors:
[auto build test ERROR on trace/for-next]
[also build test ERROR on linus/master v6.17-rc4 next-20250905]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Fidal-Palamparambil/Fixed-the-build-warning-in-init_trace_printk_function_export/20250907-221041
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/20250907140755.529-1-rootuserhere%40gmail.com
patch subject: [PATCH] Fixed the build warning in init_trace_printk_function_export():
config: x86_64-buildonly-randconfig-002-20250907 (https://download.01.org/0day-ci/archive/20250908/202509080203.SxCdQOOY-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250908/202509080203.SxCdQOOY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509080203.SxCdQOOY-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/trace_printk.c:369:18: error: passing 'const struct file *' to parameter of type 'struct file *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
369 | return seq_open(file, &show_format_seq_ops);
| ^~~~
include/linux/seq_file.h:108:27: note: passing argument to parameter here
108 | int seq_open(struct file *, const struct seq_operations *);
| ^
>> kernel/trace/trace_printk.c:373:10: error: incompatible function pointer types initializing 'int (*)(struct inode *, struct file *)' with an expression of type 'int (struct inode *, const struct file *)' [-Wincompatible-function-pointer-types]
373 | .open = ftrace_formats_open,
| ^~~~~~~~~~~~~~~~~~~
2 errors generated.
vim +369 kernel/trace/trace_printk.c
7975a2be16dd42 Steven Rostedt 2009-03-12 359
7975a2be16dd42 Steven Rostedt 2009-03-12 360 static int
66670b02cb828c Fidal palamparambil 2025-09-07 361 ftrace_formats_open(struct inode *inode, const struct file *file)
7975a2be16dd42 Steven Rostedt 2009-03-12 362 {
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 363) int ret;
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 364)
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 365) ret = security_locked_down(LOCKDOWN_TRACEFS);
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 366) if (ret)
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 367) return ret;
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 368)
c8961ec6da22ea Li Zefan 2009-06-24 @369 return seq_open(file, &show_format_seq_ops);
7975a2be16dd42 Steven Rostedt 2009-03-12 370 }
7975a2be16dd42 Steven Rostedt 2009-03-12 371
7975a2be16dd42 Steven Rostedt 2009-03-12 372 static const struct file_operations ftrace_formats_fops = {
7975a2be16dd42 Steven Rostedt 2009-03-12 @373 .open = ftrace_formats_open,
7975a2be16dd42 Steven Rostedt 2009-03-12 374 .read = seq_read,
7975a2be16dd42 Steven Rostedt 2009-03-12 375 .llseek = seq_lseek,
7975a2be16dd42 Steven Rostedt 2009-03-12 376 .release = seq_release,
7975a2be16dd42 Steven Rostedt 2009-03-12 377 };
7975a2be16dd42 Steven Rostedt 2009-03-12 378
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-07 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 14:07 Fidal Palamparambil
2025-09-07 17:01 ` kernel test robot
2025-09-07 18:33 ` kernel test robot [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=202509080203.SxCdQOOY-lkp@intel.com \
--to=lkp@intel.com \
--cc=da.gomez@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=petr.pavlu@suse.com \
--cc=rootuserhere@gmail.com \
--cc=samitolvanen@google.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
all inboxes | Powered by JetHome®