In message: [V2][linux-yocto][v5.10/standard/preempt-rt/base][PATCH] net: 
replace raw_write_seqcount_t_begin by do_raw_write_seqcount_begin
on 26/10/2023 Li Wang wrote:

> From: "Luis Claudio R. Goncalves" <lgonc...@redhat.com>
> 
> commit 3b5b679fc12ca9aa310862d5f0a6e23d6151c6a4 linux-stable-rt v5.10-rt-next
> 
> Commit a8dd21118b0fa ("seqlock: Prefix internal seqcount_t-only macros with a
> "do_""), among other changes, renames the function raw_write_seqcount_t_begin
> to do_raw_write_seqcount_begin. That commit did not cover the changes from
> the RT-only commit 81ce24cd24a9e ("net: Properly annotate the try-lock for the
> seqlock"), which are fixed here.

Thanks! this long log explains the issue much more clearly.

This is now merged.

Bruce

> 
> Fixes: 81ce24cd24a9e ("net: Properly annotate the try-lock for the seqlock")
> Signed-off-by: Luis Claudio R. Goncalves <lgonc...@redhat.com>
> Signed-off-by: Li Wang <li.w...@windriver.com>
> ---
>  include/net/sch_generic.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h
> index 72be68652bb8..eee11a1c9321 100644
> --- a/include/net/sch_generic.h
> +++ b/include/net/sch_generic.h
> @@ -195,7 +195,7 @@ static inline bool qdisc_run_begin(struct Qdisc *qdisc)
>                * Variant of write_seqcount_t_begin() telling lockdep that a
>                * trylock was attempted.
>                */
> -             raw_write_seqcount_t_begin(s);
> +             do_raw_write_seqcount_begin(s);
>               seqcount_acquire(&s->dep_map, 0, 1, _RET_IP_);
>               return true;
>       }
> -- 
> 2.25.1
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13244): 
https://lists.yoctoproject.org/g/linux-yocto/message/13244
Mute This Topic: https://lists.yoctoproject.org/mt/102196064/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/21656/624485779/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to