[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69b2616d-dfeb-4e06-8f9b-60ced06cca00@lunn.ch>
Date: Sun, 16 Apr 2023 16:52:26 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Shmuel Hazan <shmuel.h@...lu.com>
Cc: "linux@...linux.org.uk" <linux@...linux.org.uk>,
"mw@...ihalf.com" <mw@...ihalf.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: [RFC PATCH] net: mvpp2: tai: add refcount for ptp worker
> diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> b/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> index 95862aff49f1..1b57573dd866 100644
> --- a/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> +++ b/drivers/net/ethernet/marvell/mvpp2/mvpp2_tai.c
> @@ -61,6 +61,7 @@ struct mvpp2_tai {
> u64 period; // nanosecond period in 32.32 fixed
> point
> /* This timestamp is updated every two seconds */
> struct timespec64 stamp;
> + u16 poll_worker_refcount;
What lock is protecting this? It would be nice to comment in the
commit message why it is safe to use a simple u16.
Andrew
Powered by blists - more mailing lists