From: Helge Deller <deller@gmx.de>
To: kernel test robot <lkp@intel.com>,
linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/3] proc: Add get_task_cmdline_kernel() function
Date: Sun, 7 Aug 2022 17:11:00 +0200 [thread overview]
Message-ID: <16c2a025-0295-4b45-daa5-aae1ca7fefc9@gmx.de> (raw)
In-Reply-To: <202208072219.zrLROtui-lkp@intel.com>
On 8/7/22 16:28, kernel test robot wrote:
> Hi Helge,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on tip/x86/mm]
> [also build test WARNING on linus/master]
> [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]
> [...]
> include/linux/proc_fs.h:222:72: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
> static inline void get_task_cmdline_kernel(struct task_struct *, char *, size_t) { }
> ^
Will fix.
Thanks!
Helge
next prev parent reply other threads:[~2022-08-07 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 15:20 [PATCH 0/3] Dump command line of faulting process to syslog Helge Deller
2022-08-01 15:20 ` [PATCH 1/3] proc: Add get_task_cmdline_kernel() function Helge Deller
2022-08-07 14:28 ` kernel test robot
2022-08-07 15:11 ` Helge Deller [this message]
2022-08-01 15:20 ` [PATCH 2/3] lib/dump_stack: Add dump_stack_print_cmdline() and wire up in dump_stack_print_info() Helge Deller
2022-08-06 14:40 ` [lib/dump_stack] 9ac328fc55: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c kernel test robot
2022-08-01 15:20 ` [PATCH 3/3] x86/fault: Dump command line of faulting process to syslog Helge Deller
2022-08-01 16:57 ` [PATCH 0/3] " Josh Triplett
2022-08-02 19:40 ` Helge Deller
2022-08-04 8:09 ` Josh Triplett
2022-08-04 8:39 ` Helge Deller
2022-08-04 9:06 ` Josh Triplett
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=16c2a025-0295-4b45-daa5-aae1ca7fefc9@gmx.de \
--to=deller@gmx.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).