OK, picked up all 4:
patches/byungchul_park-llist-provide_a_safe_version_for_llist_for_each.patch
patches/byungchul_park-sched-don_t_reinvent_the_wheel_but_use_existing_llist_api.patch
patches/byungchul_park-sched_rt-remove_unnecessary_condition_in_push_rt_task.patch
OK, picked up all 4:
patches/byungchul_park-llist-provide_a_safe_version_for_llist_for_each.patch
patches/byungchul_park-sched-don_t_reinvent_the_wheel_but_use_existing_llist_api.patch
patches/byungchul_park-sched_rt-remove_unnecessary_condition_in_push_rt_task.patch
On Fri, May 12, 2017 at 09:36:56AM +0900, Byungchul Park wrote:
> Sometimes we have to dereference next field of llist node before entering
> loop becasue the node might be deleted or the next field might be
> modified within the loop. So this adds the safe version of llist_for_each,
> that is,
On Fri, May 12, 2017 at 09:36:56AM +0900, Byungchul Park wrote:
> Sometimes we have to dereference next field of llist node before entering
> loop becasue the node might be deleted or the next field might be
> modified within the loop. So this adds the safe version of llist_for_each,
> that is,
On Fri, May 12, 2017 at 09:36:56AM +0900, Byungchul Park wrote:
> Sometimes we have to dereference next field of llist node before entering
> loop becasue the node might be deleted or the next field might be
> modified within the loop. So this adds the safe version of llist_for_each,
> that is,
On Fri, May 12, 2017 at 09:36:56AM +0900, Byungchul Park wrote:
> Sometimes we have to dereference next field of llist node before entering
> loop becasue the node might be deleted or the next field might be
> modified within the loop. So this adds the safe version of llist_for_each,
> that is,
Sometimes we have to dereference next field of llist node before entering
loop becasue the node might be deleted or the next field might be
modified within the loop. So this adds the safe version of llist_for_each,
that is, llist_for_each_safe.
Signed-off-by: Byungchul Park
Sometimes we have to dereference next field of llist node before entering
loop becasue the node might be deleted or the next field might be
modified within the loop. So this adds the safe version of llist_for_each,
that is, llist_for_each_safe.
Signed-off-by: Byungchul Park
Reviewed-by: "Huang,
8 matches
Mail list logo
