From bf4b940a87dbe94dc2e76483cfd702bacd5dbc34 Mon Sep 17 00:00:00 2001 From: Andrew Deason Date: Wed, 29 Jun 2022 17:18:01 -0500 Subject: [PATCH] CODING: Fix a couple of typos Change-Id: I2792f710a4bc61ea755b5231a9819971754ed808 Reviewed-on: https://gerrit.openafs.org/15046 Reviewed-by: Cheyenne Wills Tested-by: BuildBot Reviewed-by: Mark Vitale Reviewed-by: Benjamin Kaduk --- CODING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CODING b/CODING index e0a81f8..1bd62ba 100644 --- a/CODING +++ b/CODING @@ -306,13 +306,13 @@ the fix is to mark that warning as ignored, but only for clang. For example: # endif #endif -If the source cannot be changed to add a pragma, you might be abe to use the +If the source cannot be changed to add a pragma, you might be able to use the autoconf function AX_APPEND_COMPILE_FLAGS to create a new macro that disables the warning and then use macro for the build options for that file. For an example, see how the autoconf macro CFLAGS_NOIMPLICIT_FALLTHROUGH is defined and used. -Finally if there isn't a way to disable the specific warning, you will need to +Finally, if there isn't a way to disable the specific warning, you will need to disable all warnings for the file in question. You can do this by supplying the autoconf macro @CFLAGS_NOERROR@ in the build options for the file. For example: -- 1.9.4