From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: [PATCH 2/5] drm/print: Unconfuse kerneldoc Date: Thu, 14 Dec 2017 21:30:51 +0100 Message-ID: <20171214203054.20141-3-daniel.vetter@ffwll.ch> References: <20171214203054.20141-1-daniel.vetter@ffwll.ch> Return-path: In-Reply-To: <20171214203054.20141-1-daniel.vetter@ffwll.ch> Sender: linux-doc-owner@vger.kernel.org To: DRI Development Cc: Intel Graphics Development , Daniel Vetter , linux-doc@vger.kernel.org, Jonathan Corbet , Daniel Vetter List-Id: intel-gfx@lists.freedesktop.org It thinks we want to document the __printf(2,0) annotion. Not sure we want to teach it about all possible gcc-only flags, hence why I opted for the cheap trick of just moving it ahead of the kerneldoc. This is only a problem for static inline functions, since for non-inline function the kerneldoc is in the .c file, but the special annotations are all in the header. Cc'ing kernel-doc maintainers as fyi. Cc: linux-doc@vger.kernel.org Cc: Jonathan Corbet Signed-off-by: Daniel Vetter --- include/drm/drm_print.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h index 5f9932e2246e..2a4a42e59a47 100644 --- a/include/drm/drm_print.h +++ b/include/drm/drm_print.h @@ -80,13 +80,13 @@ void __drm_printfn_debug(struct drm_printer *p, struct va_format *vaf); __printf(2, 3) void drm_printf(struct drm_printer *p, const char *f, ...); +__printf(2, 0) /** * drm_vprintf - print to a &drm_printer stream * @p: the &drm_printer * @fmt: format string * @va: the va_list */ -__printf(2, 0) static inline void drm_vprintf(struct drm_printer *p, const char *fmt, va_list *va) { -- 2.15.1