The loop in libb/kobj_uevent.c that checked for KOBBJ_MAX is no longer
present, we do a much more sane ARRAY_SIZE() check instead. See
5c5daf657cb5 ("Driver core: exclude kobject_uevent.c for
!CONFIG_HOTPLUG").
Signed-off-by: Garrit Franke
---
include/linux/kobject.h | 1 -
1 file
The loop in lib/kobject_uevent.c that checked for KOBJ_MAX is no longer
present, we do
a much more sane ARRAY_SIZE() check instead (see 5c5daf657cb5).
Therefore, the KOBJ_MAX is not used anymore.
Signed-off-by: Garrit Franke
---
include/linux/kobject.h | 1 -
1 file changed, 1 deletion
I noticed that the KOBJ_MAX action is never used. Does it serve any
purpose, or can it be removed? As far as I know, Kobjects shouldn't be
used for drivers and more higher level abstraction layers, so I figured
it isn't used by user-provided code either.
Regards
Garrit Franke
Sig
Hi all, newbie here.
Can the BIT macro be safely used on other parts of the kernel as well?
Just using git grep "1 <<" returns a ton of results where bit shifting
is used the old fashioned way.
Am Do., 18. Juni 2020 um 16:23 Uhr schrieb Liviu Dudau :
>
> On Thu, Jun 18, 2020 at 01:50:34PM +0100, C
4 matches
Mail list logo