[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220906081211.i6r3fhopkd76w7vw@nostramo>
Date: Tue, 6 Sep 2022 10:12:11 +0200
From: Michał Winiarski <michal.winiarski@...el.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
CC: <dri-devel@...ts.freedesktop.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, David Airlie <airlied@...ux.ie>,
"Daniel Vetter" <daniel@...ll.ch>,
Maxime Ripard <mripard@...nel.org>,
David Gow <davidgow@...gle.com>,
Javier Martinez Canillas <javierm@...hat.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Jonathan Corbet <corbet@....net>,
José Expósito <jose.exposito89@...il.com>
Subject: Re: [PATCH] drm/doc: Custom Kconfig for KUnit is no longer needed
On Tue, Sep 06, 2022 at 08:37:00AM +0700, Bagas Sanjaya wrote:
> On 9/6/22 01:47, Michał Winiarski wrote:
> > References: commit 6fc3a8636a7b ("kunit: tool: Enable virtio/PCI by default on UML")
>
> Use Fixes: tag for bugfix patches instead.
Can documentation update (when the referenced patch didn't touch the docs)
really be treated as a bugfix?
Or is it just a reference, validating the reasoning behind this patch?
-Michał
>
> --
> An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists