[PATCH] kernel32: Export kernel32's FlushFileBuffers() implementation.

[Francois Gouget]

kernel32 should export its own implementation now that it has been
moved back from kernelbase.

Signed-off-by: Francois Gouget 
---
 dlls/kernel32/kernel32.spec | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dlls/kernel32/kernel32.spec b/dlls/kernel32/kernel32.spec
index f9295dc3ee4..47c7d63761c 100644
--- a/dlls/kernel32/kernel32.spec
+++ b/dlls/kernel32/kernel32.spec
@@ -516,7 +516,7 @@
 @ stdcall -import FlsGetValue(long)
 @ stdcall -import FlsSetValue(long ptr)
 @ stdcall FlushConsoleInputBuffer(long)
-@ stdcall -import FlushFileBuffers(long)
+@ stdcall FlushFileBuffers(long) KERNEL32_FlushFileBuffers
 @ stdcall -import FlushInstructionCache(long long long)
 @ stdcall FlushProcessWriteBuffers()
 @ stdcall -import FlushViewOfFile(ptr long)

[Marvin]

Hi,

While running your changed tests, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?

Full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=64499

Your paranoid android.

=== debian10 (32 bit report) ===

kernel32:
debugger.c:305: Test failed: GetThreadContext failed: 5

=== debian10 (32 bit Chinese:China report) ===

kernel32:
comm.c:918: Test failed: OutQueue should not be empty

=== debian10 (32 bit WoW report) ===

kernel32:
change.c:320: Test failed: should be ready
comm.c:918: Test failed: OutQueue should not be empty
debugger: Timeout

[Francois Gouget]

On Tue, 4 Feb 2020, Marvin wrote:
[...]
> === debian10 (32 bit report) ===
>
> kernel32:
> debugger.c:305: Test failed: GetThreadContext failed: 5

This is a known random failure:
https://bugs.winehq.org/show_bug.cgi?id=48091
> === debian10 (32 bit Chinese:China report) ===
>
> kernel32:
> comm.c:918: Test failed: OutQueue should not be empty

QEmu's serial baud rate bug:
https://bugs.winehq.org/show_bug.cgi?id=48108
> === debian10 (32 bit WoW report) ===
>
> kernel32:
> change.c:320: Test failed: should be ready

Random failure:
https://test.winehq.org/data/287dabd9b6887e94cabfa2a5f9bfe822522095e5/linux_...
> debugger: Timeout

A different random kernel32:debugger failure:
https://test.winehq.org/data/87875e12bcdca659e578849fa62585b1b5316a50/win10_...
> comm.c:918: Test failed: OutQueue should not be empty

QEmu again.

Just a few more days and these false positives should be a thing of the 
past.