greybus-dev November 2025

greybus-dev@lists.linaro.org

17 participants
50 discussions

Re: [PATCH v2] staging: greybus: audio_manager_module: make envp array static const

by kernel test robot

Hi Chang, kernel test robot noticed the following build errors: [auto build test ERROR on staging/staging-testing] url: https://github.com/intel-lab-lkp/linux/commits/Chang-Junzheng/staging-greyb… base: staging/staging-testing patch link: https://lore.kernel.org/r/tencent_3725607DD617A567779DEB1BEC7C3B335208%40qq… patch subject: [PATCH v2] staging: greybus: audio_manager_module: make envp array static const config: arm-randconfig-001-20251114 (https://download.01.org/0day-ci/archive/20251114/202511140945.OPHTq1yc-lkp@…) compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251114/202511140945.OPHTq1yc-lkp@…) 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(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202511140945.OPHTq1yc-lkp@intel.com/ All errors (new ones prefixed by >>): drivers/staging/greybus/audio_manager_module.c: In function 'send_add_uevent': >> drivers/staging/greybus/audio_manager_module.c:163:9: error: initializer element is not constant 163 | name_string, | ^~~~~~~~~~~ drivers/staging/greybus/audio_manager_module.c:163:9: note: (near initialization for 'envp[0]') drivers/staging/greybus/audio_manager_module.c:164:9: error: initializer element is not constant 164 | vid_string, | ^~~~~~~~~~ drivers/staging/greybus/audio_manager_module.c:164:9: note: (near initialization for 'envp[1]') drivers/staging/greybus/audio_manager_module.c:165:9: error: initializer element is not constant 165 | pid_string, | ^~~~~~~~~~ drivers/staging/greybus/audio_manager_module.c:165:9: note: (near initialization for 'envp[2]') drivers/staging/greybus/audio_manager_module.c:166:9: error: initializer element is not constant 166 | intf_id_string, | ^~~~~~~~~~~~~~ drivers/staging/greybus/audio_manager_module.c:166:9: note: (near initialization for 'envp[3]') drivers/staging/greybus/audio_manager_module.c:167:9: error: initializer element is not constant 167 | ip_devices_string, | ^~~~~~~~~~~~~~~~~ drivers/staging/greybus/audio_manager_module.c:167:9: note: (near initialization for 'envp[4]') drivers/staging/greybus/audio_manager_module.c:168:9: error: initializer element is not constant 168 | op_devices_string, | ^~~~~~~~~~~~~~~~~ drivers/staging/greybus/audio_manager_module.c:168:9: note: (near initialization for 'envp[5]') >> drivers/staging/greybus/audio_manager_module.c:181:53: error: passing argument 3 of 'kobject_uevent_env' from incompatible pointer type [-Wincompatible-pointer-types] 181 | kobject_uevent_env(&module->kobj, KOBJ_ADD, envp); | ^~~~ | | | const char * const* In file included from drivers/staging/greybus/audio_manager.h:11, from drivers/staging/greybus/audio_manager_module.c:10: include/linux/kobject.h:216:31: note: expected 'char **' but argument is of type 'const char * const*' 216 | char *envp[]); | ~~~~~~^~~~~~ vim +163 drivers/staging/greybus/audio_manager_module.c 8db00736d365b7 Svetlin Ankov 2016-01-13 152 8db00736d365b7 Svetlin Ankov 2016-01-13 153 static void send_add_uevent(struct gb_audio_manager_module *module) 8db00736d365b7 Svetlin Ankov 2016-01-13 154 { 8db00736d365b7 Svetlin Ankov 2016-01-13 155 char name_string[128]; 8db00736d365b7 Svetlin Ankov 2016-01-13 156 char vid_string[64]; 8db00736d365b7 Svetlin Ankov 2016-01-13 157 char pid_string[64]; d0af1bd5f6f449 Pankaj Bharadiya 2016-10-16 158 char intf_id_string[64]; a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 159 char ip_devices_string[64]; a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 160 char op_devices_string[64]; 8db00736d365b7 Svetlin Ankov 2016-01-13 161 9af5fbe96477a4 Chang Junzheng 2025-11-13 162 static const char * const envp[] = { 8db00736d365b7 Svetlin Ankov 2016-01-13 @163 name_string, 8db00736d365b7 Svetlin Ankov 2016-01-13 164 vid_string, 8db00736d365b7 Svetlin Ankov 2016-01-13 165 pid_string, d0af1bd5f6f449 Pankaj Bharadiya 2016-10-16 166 intf_id_string, a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 167 ip_devices_string, a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 168 op_devices_string, 8db00736d365b7 Svetlin Ankov 2016-01-13 169 NULL 8db00736d365b7 Svetlin Ankov 2016-01-13 170 }; 8db00736d365b7 Svetlin Ankov 2016-01-13 171 8db00736d365b7 Svetlin Ankov 2016-01-13 172 snprintf(name_string, 128, "NAME=%s", module->desc.name); 8db00736d365b7 Svetlin Ankov 2016-01-13 173 snprintf(vid_string, 64, "VID=%d", module->desc.vid); 8db00736d365b7 Svetlin Ankov 2016-01-13 174 snprintf(pid_string, 64, "PID=%d", module->desc.pid); d0af1bd5f6f449 Pankaj Bharadiya 2016-10-16 175 snprintf(intf_id_string, 64, "INTF_ID=%d", module->desc.intf_id); a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 176 snprintf(ip_devices_string, 64, "I/P DEVICES=0x%X", a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 177 module->desc.ip_devices); a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 178 snprintf(op_devices_string, 64, "O/P DEVICES=0x%X", a9234bfd6cec44 Vaibhav Agarwal 2016-03-30 179 module->desc.op_devices); 8db00736d365b7 Svetlin Ankov 2016-01-13 180 8db00736d365b7 Svetlin Ankov 2016-01-13 @181 kobject_uevent_env(&module->kobj, KOBJ_ADD, envp); 8db00736d365b7 Svetlin Ankov 2016-01-13 182 } 8db00736d365b7 Svetlin Ankov 2016-01-13 183 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 week

Re: [PATCH v2] staging: greybus: audio_manager_module: make envp array static const

by Greg Kroah-Hartman

On Thu, Nov 13, 2025 at 10:12:00PM +0800, Chang Junzheng wrote: > From: Chang Junzheng <guagua210311(a)outlook.com> > > Fix checkpatch.pl warning by changing envp array declaration to > static const char * const. This improves code safety and follows > kernel coding style recommendations. > > Signed-off-by: Chang Junzheng <guagua210311(a)qq.com> > Changes in v2: > - Restored original indentation of array elements > - Only changed the array declaration as originally intended The "Changes" goes below the --- line, as per the documentation. thanks, greg k-h

1 week

Re: [PATCH] staging: greybus: audio_manager_module: make envp array static const

by Greg Kroah-Hartman

On Thu, Nov 13, 2025 at 09:39:54PM +0800, cjz_VM wrote: > Hi Greg, > > Thanks for reviewing my patch! > > For sending twice: I apologize for the duplicate. After the first send, I realized I had missed some greybus-specific maintainers, so I resent to include them all. Then that should have been a v2 patch :) > For the indentation: You're right to ask about it. When I changed the declaration from 'char *envp[]' to 'static const char * const envp[]', the opening bracket moved to the right due to the longer declaration. I added tabs to keep the array elements aligned with the opening bracket, following the kernel coding style rule that parameters should align with the opening parenthesis. > > If this alignment approach is not preferred, I'm happy to adjust it to whatever style you recommend. You did not document your change, and it had nothing really to do with the const change, so I would not recommend doing this. Also, please do not top-post, and be sure to properly wrap your lines in your email client. thanks, greg k-h

1 week

Re: [PATCH] staging: greybus: audio_manager_module: make envp array static const

by Greg Kroah-Hartman

On Thu, Nov 13, 2025 at 09:01:46PM +0800, Chang Junzheng wrote: > From: Chang Junzheng <guagua210311(a)outlook.com> > > The envp array in send_add_uevent() function is declared as a non-const > local array, which triggers the following checkpatch.pl warning: > > WARNING: char * array declaration might be better as static const > > Change the declaration to 'static const char * const' to improve code > safety by making the array read-only and allow for better compiler > optimization. This follows the kernel coding style recommendations. > > Signed-off-by: Chang Junzheng <guagua210311(a)qq.com> You sent this twice? > --- > drivers/staging/greybus/audio_manager_module.c | 16 ++++++++-------- > 1 file changed, 8 insertions(+), 8 deletions(-) > > diff --git a/drivers/staging/greybus/audio_manager_module.c b/drivers/staging/greybus/audio_manager_module.c > index 4a4dfb42f50f..ca6a2cd0bc4f 100644 > --- a/drivers/staging/greybus/audio_manager_module.c > +++ b/drivers/staging/greybus/audio_manager_module.c > @@ -159,14 +159,14 @@ static void send_add_uevent(struct gb_audio_manager_module *module) > char ip_devices_string[64]; > char op_devices_string[64]; > > - char *envp[] = { > - name_string, > - vid_string, > - pid_string, > - intf_id_string, > - ip_devices_string, > - op_devices_string, > - NULL > + static const char * const envp[] = { > + name_string, > + vid_string, > + pid_string, > + intf_id_string, > + ip_devices_string, > + op_devices_string, > + NULL Why did you indent this? thanks, greg k-h

1 week

[PATCH v2] greybus: add WQ_PERCPU to alloc_workqueue users

by Marco Crivellari

This continues the effort to refactor workqueue APIs, which began with the introduction of new workqueues and a new alloc_workqueue flag in: commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq") commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag") This change adds a new WQ_PERCPU flag to explicitly request alloc_workqueue() to be per-cpu when WQ_UNBOUND has not been specified. With the introduction of the WQ_PERCPU flag (equivalent to !WQ_UNBOUND), any alloc_workqueue() caller that doesn’t explicitly specify WQ_UNBOUND must now use WQ_PERCPU. Once migration is complete, WQ_UNBOUND can be removed and unbound will become the implicit default. Suggested-by: Tejun Heo <tj(a)kernel.org> Signed-off-by: Marco Crivellari <marco.crivellari(a)suse.com> Reviewed-by: Johan Hovold <johan(a)kernel.org> --- Changes in v2: - updated commit log removing two paragraph not strictly related to the work. - subject changed removing "drivers/" before the actual prefix. --- drivers/greybus/operation.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/greybus/operation.c b/drivers/greybus/operation.c index 54ccc434a1f7..7e12ffb2dd60 100644 --- a/drivers/greybus/operation.c +++ b/drivers/greybus/operation.c @@ -1238,7 +1238,7 @@ int __init gb_operation_init(void) goto err_destroy_message_cache; gb_operation_completion_wq = alloc_workqueue("greybus_completion", - 0, 0); + WQ_PERCPU, 0); if (!gb_operation_completion_wq) goto err_destroy_operation_cache; -- 2.51.1

1 week, 1 day

[PATCH] drivers/greybus: add WQ_PERCPU to alloc_workqueue users

by Marco Crivellari

Currently if a user enqueues a work item using schedule_delayed_work() the used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to schedule_work() that is using system_wq and queue_work(), that makes use again of WORK_CPU_UNBOUND. This lack of consistency cannot be addressed without refactoring the API. alloc_workqueue() treats all queues as per-CPU by default, while unbound workqueues must opt-in via WQ_UNBOUND. This default is suboptimal: most workloads benefit from unbound queues, allowing the scheduler to place worker threads where they’re needed and reducing noise when CPUs are isolated. This continues the effort to refactor workqueue APIs, which began with the introduction of new workqueues and a new alloc_workqueue flag in: commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq") commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag") This change adds a new WQ_PERCPU flag to explicitly request alloc_workqueue() to be per-cpu when WQ_UNBOUND has not been specified. With the introduction of the WQ_PERCPU flag (equivalent to !WQ_UNBOUND), any alloc_workqueue() caller that doesn’t explicitly specify WQ_UNBOUND must now use WQ_PERCPU. Once migration is complete, WQ_UNBOUND can be removed and unbound will become the implicit default. Suggested-by: Tejun Heo <tj(a)kernel.org> Signed-off-by: Marco Crivellari <marco.crivellari(a)suse.com> --- drivers/greybus/operation.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/greybus/operation.c b/drivers/greybus/operation.c index 54ccc434a1f7..7e12ffb2dd60 100644 --- a/drivers/greybus/operation.c +++ b/drivers/greybus/operation.c @@ -1238,7 +1238,7 @@ int __init gb_operation_init(void) goto err_destroy_message_cache; gb_operation_completion_wq = alloc_workqueue("greybus_completion", - 0, 0); + WQ_PERCPU, 0); if (!gb_operation_completion_wq) goto err_destroy_operation_cache; -- 2.51.1

1 week, 1 day

Step-by-Step Guide to Adding a Child on Cathay Pacific

by dakeem＠dotoctuvo.com

How to Add a Child to an Existing Cathay Pacific Booking Need to add a child to your Cathay Pacific reservation? Call 1-833-341-5261 to speak with a live agent who can update your booking quickly and correctly. 📞 Step 1: Prepare Your Booking Details Have ready: • Reservation number • Full names of all passengers • Child’s age and seating preference (lap or own seat) • Any special requests (bassinet, meal, guardian seating) 📞 Step 2: Call Cathay Pacific Dial 1-833-341-5261 to reach a customer support agent. Call early to avoid long wait times. 📞 Step 3: Request to Add the Child • Provide the child’s details and seating preference • Mention any extras (bassinet, special seating, meals) • Agent will confirm seat availability and any fare difference ✅ Step 4: Confirm the Update • Receive an updated itinerary by email • Review all details and fare changes • Follow up with the agent if confirmation isn’t received ✨ Tips • Call early to secure the best seats • Ask about required travel documents for infants or minors • Keep your confirmation handy for check-in Calling 1-833-341-5261 ensures a smooth, family-friendly booking update.

2 weeks

Adding Minors to Existing Cathay Pacific Trips – Guide

by dakeem＠dotoctuvo.com

2 weeks

British Airways Child Booking Made Easy – Here’s How

by dakeem＠dotoctuvo.com

How to Add a Child to an Existing British Airways Booking Need to add a child to your British Airways reservation? Call 1-833-341-5261 to speak with a live agent who can update your booking quickly and correctly. 📞 Step 1: Prepare Your Booking Details Have ready: • Reservation number • Full names of all passengers • Child’s age and seating preference (lap or own seat) • Any special requests (bassinet, meal, guardian seating) 📞 Step 2: Call British Airways Dial 1-833-341-5261 to reach a customer support agent. Call early to avoid long wait times. 📞 Step 3: Request to Add the Child • Provide the child’s details and seating preference • Mention any extras (bassinet, special seating, meals) • Agent will confirm seat availability and any fare difference ✅ Step 4: Confirm the Update • Receive an updated itinerary by email • Review all details and fare changes • Follow up with the agent if confirmation isn’t received ✨ Tips • Call early to secure the best seats • Ask about required travel documents for infants or minors • Keep your confirmation handy for check-in Calling 1-833-341-5261 ensures a smooth, family-friendly booking update.

2 weeks

Avianca Airlines Child Booking Made Easy – Here’s How

by dakeem＠dotoctuvo.com

How to Add a Child to an Existing Avianca Airlines Booking Need to add a child to your Avianca Airlines reservation? Call 1-833-341-5261 to speak with a live agent who can update your booking quickly and correctly. 📞 Step 1: Prepare Your Booking Details Have ready: • Reservation number • Full names of all passengers • Child’s age and seating preference (lap or own seat) • Any special requests (bassinet, meal, guardian seating) 📞 Step 2: Call Avianca Airlines Dial 1-833-341-5261 to reach a customer support agent. Call early to avoid long wait times. 📞 Step 3: Request to Add the Child • Provide the child’s details and seating preference • Mention any extras (bassinet, special seating, meals) • Agent will confirm seat availability and any fare difference ✅ Step 4: Confirm the Update • Receive an updated itinerary by email • Review all details and fare changes • Follow up with the agent if confirmation isn’t received ✨ Tips • Call early to secure the best seats • Ask about required travel documents for infants or minors • Keep your confirmation handy for check-in Calling 1-833-341-5261 ensures a smooth, family-friendly booking update.

2 weeks

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

greybus-dev November 2025