[driver-core:kobject-const] BUILD SUCCESS 5ccc23cddfc5a6d1a41a21e456b9ce5e8c238d53

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git kobject-const branch HEAD: 5ccc23cddfc5a6d1a41a21e456b9ce5e8c238d53 kobject: kobj_type: remove default_attrs elapsed time: 1001m configs tested: 112 configs skipped: 3 The following configs have been built

[staging:staging-testing] BUILD SUCCESS 507975d937e80796e8bb2b41f19d1e4a71ec40b7

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing branch HEAD: 507975d937e80796e8bb2b41f19d1e4a71ec40b7 staging: rtl8723bs: refactor rtw_ch2freq() elapsed time: 911m configs tested: 110 configs skipped: 3 The following configs have been built

Re: Re: [PATCH v1] pinctrl: ralink: rt2880: Check for return value of devm_kcalloc()

On Fri, Apr 1, 2022 at 6:06 AM unSimple wrote: > > The main consideration of the 'continue' in the patch is that those > statements are inner a loop. > > The next allocation may be successful so I think it is better to use > 'continue' here. Please, do not top-post! What you explained is