From: Souptick Joarder <jrdr.linux@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:pending-fixes] BUILD SUCCESS WITH WARNING c7cab83d100f5af1c10580fe567f8c29779a7e4e
Date: Sat, 28 Nov 2020 03:30:29 +0530 [thread overview]
Message-ID: <CAFqt6zZaN27rcspZKmGA2VC6L8LwAfK6EumGgjEkxKLg2q0FyQ@mail.gmail.com> (raw)
In-Reply-To: <5fc0f109.6ksPO8p2h7N3bhbY%lkp@intel.com>
On Fri, Nov 27, 2020 at 5:59 PM kernel test robot <lkp@intel.com> wrote:
>
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
> branch HEAD: c7cab83d100f5af1c10580fe567f8c29779a7e4e Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
>
> Warning in current branch:
>
> drivers/media/test-drivers/vidtv/vidtv_s302m.c:475 vidtv_s302m_encoder_init() warn: possible memory leak of 'e'
>
> Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> `-- i386-randconfig-m021-20201127
> `-- drivers-media-test-drivers-vidtv-vidtv_s302m.c-vidtv_s302m_encoder_init()-warn:possible-memory-leak-of-e
This looks like a false warning.
>
> elapsed time: 721m
>
> configs tested: 115
> configs skipped: 2
>
> gcc tested configs:
> arm defconfig
> arm64 allyesconfig
> arm64 defconfig
> arm allyesconfig
> arm allmodconfig
> h8300 h8s-sim_defconfig
> powerpc mpc834x_itx_defconfig
> sh rsk7203_defconfig
> arm lubbock_defconfig
> sparc sparc32_defconfig
> powerpc mpc837x_mds_defconfig
> arc axs101_defconfig
> mips pic32mzda_defconfig
> arm imx_v6_v7_defconfig
> powerpc64 alldefconfig
> powerpc ep88xc_defconfig
> powerpc fsp2_defconfig
> powerpc acadia_defconfig
> powerpc sam440ep_defconfig
> powerpc amigaone_defconfig
> powerpc mpc832x_rdb_defconfig
> mips loongson1b_defconfig
> powerpc gamecube_defconfig
> arm cerfcube_defconfig
> arc vdk_hs38_smp_defconfig
> arc tb10x_defconfig
> mips rb532_defconfig
> powerpc kmeter1_defconfig
> mips ip22_defconfig
> powerpc akebono_defconfig
> arm davinci_all_defconfig
> powerpc bluestone_defconfig
> mips ip32_defconfig
> c6x evmc6474_defconfig
> powerpc arches_defconfig
> x86_64 alldefconfig
> sh shx3_defconfig
> powerpc cell_defconfig
> mips decstation_r4k_defconfig
> powerpc mpc8315_rdb_defconfig
> mips decstation_defconfig
> arc hsdk_defconfig
> powerpc ppc40x_defconfig
> sh dreamcast_defconfig
> arm spear13xx_defconfig
> um kunit_defconfig
> ia64 allmodconfig
> ia64 defconfig
> ia64 allyesconfig
> m68k allmodconfig
> m68k defconfig
> m68k allyesconfig
> nios2 defconfig
> arc allyesconfig
> nds32 allnoconfig
> c6x allyesconfig
> nds32 defconfig
> nios2 allyesconfig
> csky defconfig
> alpha defconfig
> alpha allyesconfig
> xtensa allyesconfig
> h8300 allyesconfig
> arc defconfig
> sh allmodconfig
> parisc defconfig
> s390 allyesconfig
> parisc allyesconfig
> s390 defconfig
> i386 allyesconfig
> sparc allyesconfig
> sparc defconfig
> i386 defconfig
> mips allyesconfig
> mips allmodconfig
> powerpc allyesconfig
> powerpc allmodconfig
> powerpc allnoconfig
> i386 randconfig-a004-20201127
> i386 randconfig-a003-20201127
> i386 randconfig-a002-20201127
> i386 randconfig-a005-20201127
> i386 randconfig-a001-20201127
> i386 randconfig-a006-20201127
> x86_64 randconfig-a015-20201127
> x86_64 randconfig-a011-20201127
> x86_64 randconfig-a014-20201127
> x86_64 randconfig-a016-20201127
> x86_64 randconfig-a012-20201127
> x86_64 randconfig-a013-20201127
> i386 randconfig-a012-20201127
> i386 randconfig-a013-20201127
> i386 randconfig-a011-20201127
> i386 randconfig-a016-20201127
> i386 randconfig-a014-20201127
> i386 randconfig-a015-20201127
> riscv nommu_k210_defconfig
> riscv allyesconfig
> riscv nommu_virt_defconfig
> riscv allnoconfig
> riscv defconfig
> riscv rv32_defconfig
> riscv allmodconfig
> x86_64 rhel
> x86_64 allyesconfig
> x86_64 rhel-7.6-kselftests
> x86_64 defconfig
> x86_64 rhel-8.3
> x86_64 kexec
>
> clang tested configs:
> x86_64 randconfig-a006-20201127
> x86_64 randconfig-a003-20201127
> x86_64 randconfig-a004-20201127
> x86_64 randconfig-a005-20201127
> x86_64 randconfig-a002-20201127
> x86_64 randconfig-a001-20201127
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
next prev parent reply other threads:[~2020-11-27 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 12:28 kernel test robot
2020-11-27 22:00 ` Souptick Joarder [this message]
2020-11-30 8:03 ` Rong Chen
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=CAFqt6zZaN27rcspZKmGA2VC6L8LwAfK6EumGgjEkxKLg2q0FyQ@mail.gmail.com \
--to=jrdr.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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