[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v8q09943.fsf@meer.lwn.net>
Date: Tue, 06 Sep 2022 02:53:48 -0600
From: Jonathan Corbet <corbet@....net>
To: Michał Winiarski <michal.winiarski@...el.com>,
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>,
José Expósito <jose.exposito89@...il.com>
Subject: Re: [PATCH] drm/doc: Custom Kconfig for KUnit is no longer needed
Michał Winiarski <michal.winiarski@...el.com> writes:
> 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?
I kind of agree; I'm not sure that a Fixes tag is really warranted here.
Thanks,
jon
Powered by blists - more mailing lists