[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240912073828.GC572255@kernel.org>
Date: Thu, 12 Sep 2024 08:38:28 +0100
From: Simon Horman <horms@...nel.org>
To: Anna-Maria Behnsen <anna-maria@...utronix.de>
Cc: John Stultz <jstultz@...gle.com>,
Frederic Weisbecker <frederic@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Miroslav Lichvar <mlichvar@...hat.com>,
Richard Cochran <richardcochran@...il.com>,
Christopher S Hall <christopher.s.hall@...el.com>
Subject: Re: [PATCH 10/24] timekeeping: Define a struct type for tk_core to
make it reusable
On Wed, Sep 11, 2024 at 03:29:54PM +0200, Anna-Maria Behnsen wrote:
> The struct tk_core uses is not reusable. As long as there is only a single
> timekeeper, this is not a problem. But when the timekeeper infrastructure
> will be reused for per ptp clock timekeepers, an explicit struct type is
> required.
>
> Define struct tk_data as explicit struct type for tk_core.
>
> Signed-off-by: Anna-Maria Behnsen <anna-maria@...utronix.de>
...
Hi Anna-Maria,
I wonder if the order of this and the previous patch should
be reversed, or the two patches should be squashed together.
I am seeing a build failure with only patches 01-09/24 of this series
applied, which seem to be resolved by applying this patch.
.../timekeeping.c:1735:43: warning: declaration of 'struct tk_data' will not be visible outside of this function [-Wvisibility]
1735 | static __init void tkd_basic_setup(struct tk_data *tkd)
...
Powered by blists - more mailing lists