linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master] BUILD REGRESSION c34be716fb373fad4ce1d2c4462b6267158070b1
Date: Sun, 08 Dec 2019 22:33:07 +0800	[thread overview]
Message-ID: <5ded09a3.A9XGoIjntMuGa9wj%lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git  master
branch HEAD: c34be716fb373fad4ce1d2c4462b6267158070b1  Add linux-next specific files for 20191208

Regressions in current branch:

drivers/devfreq/devfreq-event.c:355: warning: Function parameter or member 'edev' not described in 'devfreq_event_remove_edev'
include/linux/devfreq.h:189: warning: Function parameter or member 'last_status' not described in 'devfreq'

Error ids grouped by kconfigs:

recent_errors
`-- i386-allnoconfig
    |-- drivers-devfreq-devfreq-event.c:warning:Function-parameter-or-member-edev-not-described-in-devfreq_event_remove_edev
    `-- include-linux-devfreq.h:warning:Function-parameter-or-member-last_status-not-described-in-devfreq

elapsed time: 340m

configs tested: 15

um                           x86_64_defconfig
um                             i386_defconfig
um                                  defconfig
parisc                        c3000_defconfig
parisc                         b180_defconfig
parisc                              defconfig
parisc                            allnoconfig
x86_64                                    lkp
x86_64                                   rhel
x86_64                              fedora-25
x86_64                                  kexec
arm64                            allmodconfig
i386                              allnoconfig
i386                                defconfig
i386                             alldefconfig

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation


                 reply	other threads:[~2019-12-08 14:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5ded09a3.A9XGoIjntMuGa9wj%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.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