From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Ceresoli Subject: [PATCH 1/2] drm/doc: fix kerneldoc syntax Date: Wed, 13 Mar 2019 16:35:36 +0100 Message-ID: <20190313153537.22654-1-luca@lucaceresoli.net> Return-path: Sender: linux-kernel-owner@vger.kernel.org To: dri-devel@lists.freedesktop.org Cc: Maarten Lankhorst , Maxime Ripard , Sean Paul , David Airlie , Daniel Vetter , linux-kernel@vger.kernel.org, Luca Ceresoli List-Id: dri-devel@lists.freedesktop.org The probe() reference renders incorrectly and without a link, fix it. Also fix a typo reported by checkpatch in the context lines. Signed-off-by: Luca Ceresoli --- drivers/gpu/drm/drm_drv.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c index 381581b01d48..585f5d079046 100644 --- a/drivers/gpu/drm/drm_drv.c +++ b/drivers/gpu/drm/drm_drv.c @@ -264,13 +264,13 @@ void drm_minor_release(struct drm_minor *minor) * DOC: driver instance overview * * A device instance for a drm driver is represented by &struct drm_device. This - * is initialized with drm_dev_init(), usually from bus-specific ->probe() - * callbacks implemented by the driver. The driver then needs to initialize all - * the various subsystems for the drm device like memory management, vblank - * handling, modesetting support and intial output configuration plus obviously - * initialize all the corresponding hardware bits. Finally when everything is up - * and running and ready for userspace the device instance can be published - * using drm_dev_register(). + * is initialized with drm_dev_init(), usually from bus-specific + * &drm_driver.probe() callbacks implemented by the driver. The driver then + * needs to initialize all the various subsystems for the drm device like memory + * management, vblank handling, modesetting support and initial output + * configuration plus obviously initialize all the corresponding hardware + * bits. Finally when everything is up and running and ready for userspace the + * device instance can be published using drm_dev_register(). * * There is also deprecated support for initalizing device instances using * bus-specific helpers and the &drm_driver.load callback. But due to -- 2.17.1