From: kernel test robot <lkp@intel.com>
To: Madhumitha Prabakaran <madhumithabiw@gmail.com>,
vaibhav.sr@gmail.com, mgreer@animalcreek.com, johan@kernel.org,
elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, skhan@linuxfoundation.org,
ivan.orlov0322@gmail.com
Subject: Re: [PATCH] staging: greybus: Refactor gb_audio_gb_get_topology() into separate calls
Date: Sat, 5 Aug 2023 06:09:36 +0800 [thread overview]
Message-ID: <202308050511.y5Yb9otW-lkp@intel.com> (raw)
In-Reply-To: <20230804203134.GA618419@madhu-kernel>
Hi Madhumitha,
kernel test robot noticed the following build warnings:
[auto build test WARNING on staging/staging-testing]
url: https://github.com/intel-lab-lkp/linux/commits/Madhumitha-Prabakaran/staging-greybus-Refactor-gb_audio_gb_get_topology-into-separate-calls/20230805-043242
base: staging/staging-testing
patch link: https://lore.kernel.org/r/20230804203134.GA618419%40madhu-kernel
patch subject: [PATCH] staging: greybus: Refactor gb_audio_gb_get_topology() into separate calls
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20230805/202308050511.y5Yb9otW-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230805/202308050511.y5Yb9otW-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/202308050511.y5Yb9otW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/staging/greybus/audio_gb.c:11:5: warning: no previous prototype for 'gb_audio_gb_get_topology_size' [-Wmissing-prototypes]
11 | int gb_audio_gb_get_topology_size(struct gb_connection *connection, u16 *size)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/staging/greybus/audio_gb.c:25:27: warning: no previous prototype for 'gb_audio_gb_alloc_topology' [-Wmissing-prototypes]
25 | struct gb_audio_topology *gb_audio_gb_alloc_topology(u16 size)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/gb_audio_gb_get_topology_size +11 drivers/staging/greybus/audio_gb.c
10
> 11 int gb_audio_gb_get_topology_size(struct gb_connection *connection, u16 *size)
12 {
13 struct gb_audio_get_topology_size_response size_resp;
14 int ret;
15
16 ret = gb_operation_sync(connection, GB_AUDIO_TYPE_GET_TOPOLOGY_SIZE,
17 NULL, 0, &size_resp, sizeof(size_resp));
18 if (ret)
19 return ret;
20
21 *size = le16_to_cpu(size_resp.size);
22 return 0;
23 }
24
> 25 struct gb_audio_topology *gb_audio_gb_alloc_topology(u16 size)
26 {
27 struct gb_audio_topology *topo;
28
29 if (size < sizeof(struct gb_audio_topology))
30 return NULL;
31
32 topo = kzalloc(size, GFP_KERNEL);
33 return topo;
34 }
35
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-04 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 20:31 [PATCH] staging: greybus: Refactor gb_audio_gb_get_topology() into separate calls Madhumitha Prabakaran
2023-08-04 22:09 ` kernel test robot [this message]
2023-08-05 16:14 ` Dan Carpenter
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=202308050511.y5Yb9otW-lkp@intel.com \
--to=lkp@intel.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=ivan.orlov0322@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=madhumithabiw@gmail.com \
--cc=mgreer@animalcreek.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=vaibhav.sr@gmail.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