diff options
| author | Laszlo Ersek <lersek@redhat.com> | 2023-10-12 11:10:56 +0200 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2023-10-18 16:15:41 +0000 |
| commit | 3c3136d3b6ae2976cbe05ff2b8f23ae58b780034 (patch) | |
| tree | d2192b8454518bfc230121b6f86a8819c3699cc7 /EmbeddedPkg/Include/Library/RealTimeClockLib.h | |
| parent | e6e0e7ba74b670564efea79e628207f5f76ce743 (diff) | |
| download | edk2-3c3136d3b6ae2976cbe05ff2b8f23ae58b780034.tar.gz edk2-3c3136d3b6ae2976cbe05ff2b8f23ae58b780034.tar.bz2 edk2-3c3136d3b6ae2976cbe05ff2b8f23ae58b780034.zip | |
EmbeddedPkg/VirtualRealTimeClockLib: drop LibRtcVirtualNotifyEvent
The RealTimeClockLib class header in edk2 mistakenly declares a function
called LibRtcVirtualNotifyEvent(). No component ever calls this function
crossing module boundaries; all RealTimeClockLib instances in edk2 and
edk2-platforms are supposed to register (and do register) their
SetVirtualAddressMap() notification functions.
In particular, VirtualRealTimeClockLib *itself* doesn't even use
LibRtcVirtualNotifyEvent() -- the function is defined with an empty body,
clearly in an understandable, but misguided, attempt, to conform to the
(bogus) library interface. Remove the function.
Build-tested only (with "RiscVVirtQemu.dsc").
Cc: Abner Chang <abner.chang@amd.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Daniel Schaefer <git@danielschaefer.me>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>
Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=4564
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Message-Id: <20231012091057.108728-5-lersek@redhat.com>
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'EmbeddedPkg/Include/Library/RealTimeClockLib.h')
0 files changed, 0 insertions, 0 deletions