From: kernel test robot <lkp@intel.com>
To: Daniel Latypov <dlatypov@google.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>
Subject: [linux-next:master 11060/11651] lib/kunit/executor.c:73:8-15: WARNING opportunity for kmemdup
Date: Sat, 14 May 2022 21:49:30 +0800 [thread overview]
Message-ID: <202205142103.OR7vREzO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1e1b28b936aed946122b4e0991e7144fdbbfd77e
commit: a02353f491622e49c7ddedc6a6dc4f1d6ed2150a [11060/11651] kunit: bail out of test filtering logic quicker if OOM
config: sparc64-randconfig-c004-20220512 (https://download.01.org/0day-ci/archive/20220514/202205142103.OR7vREzO-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 11.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cocci warnings: (new ones prefixed by >>)
>> lib/kunit/executor.c:73:8-15: WARNING opportunity for kmemdup
Please review and possibly fold the followup patch.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-14 13:50 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=202205142103.OR7vREzO-lkp@intel.com \
--to=lkp@intel.com \
--cc=brendanhiggins@google.com \
--cc=dlatypov@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.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