[driver-core:kobject-const] BUILD SUCCESS d07be11e5af511b121ca7fb623a356fab1349c65

2022-11-23 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git kobject-const branch HEAD: d07be11e5af511b121ca7fb623a356fab1349c65 kobject: kset_uevent_ops: make uevent() callback take a const * elapsed time: 914m configs tested: 79 configs skipped: 2 The following

Re: [PATCH v3 1/1] binder: return pending info for frozen async txns

2022-11-23 Thread Carlos Llamas
On Wed, Nov 23, 2022 at 12:16:54PM -0800, Li Li wrote: > From: Li Li > > An async transaction to a frozen process will still be successfully > put in the queue. But this pending async transaction won't be processed > until the target process is unfrozen at an unspecified time in the > future.

[driver-core:kobject-const2] BUILD REGRESSION a24f87696c63e8564c4e04b8715daaca5e2144c9

2022-11-23 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git kobject-const2 branch HEAD: a24f87696c63e8564c4e04b8715daaca5e2144c9 driver core: device_get_devnode() should take a const * Error/Warning reports:

Re: [PATCH v2 1/1] binder: return pending info for frozen async txns

2022-11-23 Thread Li Li
On Wed, Nov 23, 2022 at 10:58 AM Carlos Llamas wrote: > > This looks good. Could you rename the new op to signify the frozen > scenario though? We might have some other instances of pending > transactions in the future so might as well be specific here. Done [1]. v3: rename

[PATCH v3 1/1] binder: return pending info for frozen async txns

2022-11-23 Thread Li Li
From: Li Li An async transaction to a frozen process will still be successfully put in the queue. But this pending async transaction won't be processed until the target process is unfrozen at an unspecified time in the future. Pass this important information back to the user space caller by

[PATCH v3 0/1] binder: return pending info for frozen async txns

2022-11-23 Thread Li Li
From: Li Li User applications need to know if their binder transactions reach a frozen process or not. For sync binder calls, Linux kernel already has a dedicated return value BR_FROZEN_REPLY, indicating this sync binder transaction will be rejected (similar to BR_DEAD_REPLY) as the target

Re: [PATCH v2 1/1] binder: return pending info for frozen async txns

2022-11-23 Thread Carlos Llamas
On Thu, Nov 10, 2022 at 12:34:05PM -0800, Li Li wrote: > From: Li Li > > An async transaction to a frozen process will still be successfully > put in the queue. But this pending async transaction won't be processed > until the target process is unfrozen at an unspecified time in the > future.

[staging:staging-testing] BUILD SUCCESS 9dadff066244543780e5d9ee406b3ec7af19e22c

2022-11-23 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing branch HEAD: 9dadff066244543780e5d9ee406b3ec7af19e22c staging: iio: ade7854: Convert to i2c's .probe_new() elapsed time: 1527m configs tested: 78 configs skipped: 2 The following configs have been

[driver-core:driver-core-testing] BUILD SUCCESS 9f041c5d8296b3a04cf3ead473a124fb538490dc

2022-11-23 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git driver-core-testing branch HEAD: 9f041c5d8296b3a04cf3ead473a124fb538490dc driver core: pass a const * into of_device_uevent() elapsed time: 1024m configs tested: 99 configs skipped: 3 The following configs