From: kernel test robot <lkp@intel.com>
To: Yi Yang <yiyang13@huawei.com>,
miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, u.kleine-koenig@pengutronix.de,
tudor.ambarus@linaro.org, robh@kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3] mtd: powernv_flash: check return value of devm_kasprintf()
Date: Thu, 19 Oct 2023 17:00:31 +0800 [thread overview]
Message-ID: <202310191650.ib8cKENG-lkp@intel.com> (raw)
In-Reply-To: <20231019065618.318495-1-yiyang13@huawei.com>
Hi Yi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mtd/mtd/next]
[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]
url: https://github.com/intel-lab-lkp/linux/commits/Yi-Yang/mtd-powernv_flash-check-return-value-of-devm_kasprintf/20231019-145927
base: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next
patch link: https://lore.kernel.org/r/20231019065618.318495-1-yiyang13%40huawei.com
patch subject: [PATCH v3] mtd: powernv_flash: check return value of devm_kasprintf()
reproduce: (https://download.01.org/0day-ci/archive/20231019/202310191650.ib8cKENG-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310191650.ib8cKENG-lkp@intel.com/
# many are suggestions rather than must-fix
ERROR:TRAILING_WHITESPACE: trailing whitespace
#26: FILE: drivers/mtd/devices/powernv_flash.c:212:
+^I$
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-10-19 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 6:56 [PATCH v3] mtd: powernv_flash: check return value of devm_kasprintf() Yi Yang
2023-10-19 6:56 ` Yi Yang
2023-10-19 9:00 ` kernel test robot [this message]
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=202310191650.ib8cKENG-lkp@intel.com \
--to=lkp@intel.com \
--cc=christophe.leroy@csgroup.eu \
--cc=miquel.raynal@bootlin.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@ti.com \
--cc=yiyang13@huawei.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 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.