All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [CFT][PATCH] exit/bdflush: Remove the deprecated bdflush system call
Date: Wed, 30 Jun 2021 05:55:25 +0800	[thread overview]
Message-ID: <202106300518.XTzRgogX-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]

CC: kbuild-all(a)lists.01.org
In-Reply-To: <87sg10quue.fsf_-_@disp2133>
References: <87sg10quue.fsf_-_@disp2133>
TO: "Eric W. Biederman" <ebiederm@xmission.com>
TO: Michael Schmitz <schmitzmic@gmail.com>
CC: Geert Uytterhoeven <geert@linux-m68k.org>
CC: Al Viro <viro@zeniv.linux.org.uk>
CC: "linux-arch" <linux-arch@vger.kernel.org>
CC: Jens Axboe <axboe@kernel.dk>
CC: Oleg Nesterov <oleg@redhat.com>
CC: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
CC: Richard Henderson <rth@twiddle.net>
CC: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
CC: Matt Turner <mattst88@gmail.com>

Hi "Eric,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on tip/perf/core]
[also build test WARNING on arm64/for-next/core m68k/for-next hp-parisc/for-next powerpc/next s390/features tip/x86/asm linus/master sparc/master v5.13 next-20210629]
[cannot apply to sparc-next/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]

url:    https://github.com/0day-ci/linux/commits/Eric-W-Biederman/exit-bdflush-Remove-the-deprecated-bdflush-system-call/20210630-042915
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 012669c740e6e2afa8bdb95394d06676f933dd2d
:::::: branch date: 86 minutes ago
:::::: commit date: 86 minutes ago
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
cd tools/perf && ./check-headers.sh

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


perfheadercheck warnings: (new ones prefixed by >>)
>> Warning: Kernel ABI header at 'tools/perf/arch/s390/entry/syscalls/syscall.tbl' differs from latest version at 'arch/s390/kernel/syscalls/syscall.tbl':  125< 134  common	bdflush			-				-
>> Warning: Kernel ABI header at 'tools/perf/arch/s390/entry/syscalls/syscall.tbl' differs from latest version at 'arch/s390/kernel/syscalls/syscall.tbl':  125> 134  common	bdflush			sys_ni_syscall			sys_ni_syscall

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

             reply	other threads:[~2021-06-29 21:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 21:55 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-21 13:54 Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads Al Viro
2021-06-21 18:59 ` Al Viro
2021-06-21 19:22   ` Linus Torvalds
2021-06-21 20:03     ` Eric W. Biederman
2021-06-21 23:15       ` Linus Torvalds
2021-06-22 20:52         ` Eric W. Biederman
2021-06-23  0:41           ` Linus Torvalds
2021-06-23 14:33             ` Eric W. Biederman
2021-06-24 18:57               ` [PATCH 0/9] Refactoring exit Eric W. Biederman
2021-06-24 22:45                 ` Al Viro
2021-06-27 22:13                   ` Al Viro
2021-06-27 22:59                     ` Michael Schmitz
2021-06-28  7:31                       ` Geert Uytterhoeven
2021-06-28 17:14                         ` Michael Schmitz
2021-06-28 19:17                           ` Geert Uytterhoeven
2021-06-28 20:13                             ` Michael Schmitz
2021-06-28 21:18                               ` Geert Uytterhoeven
2021-06-28 23:42                                 ` Michael Schmitz
2021-06-29 20:28                                   ` [CFT][PATCH] exit/bdflush: Remove the deprecated bdflush system call Eric W. Biederman
2021-06-29 20:28                                     ` Eric W. Biederman
2021-06-29 21:45                                     ` Michael Schmitz
2021-06-29 21:45                                       ` Michael Schmitz
2021-06-30  8:24                                     ` Geert Uytterhoeven
2021-06-30  8:37                                     ` Arnd Bergmann
2021-06-30 12:30                                     ` Cyril Hrubis

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=202106300518.XTzRgogX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild@lists.01.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 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.