public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, "David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Maxime Ripard" <mripard@kernel.org>,
	"David Gow" <davidgow@google.com>,
	"Javier Martinez Canillas" <javierm@redhat.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"José Expósito" <jose.exposito89@gmail.com>
Subject: Re: [PATCH] drm/doc: Custom Kconfig for KUnit is no longer needed
Date: Tue, 06 Sep 2022 02:53:48 -0600	[thread overview]
Message-ID: <87v8q09943.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220906081211.i6r3fhopkd76w7vw@nostramo>

Michał Winiarski <michal.winiarski@intel.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

  reply	other threads:[~2022-09-06  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 18:47 [PATCH] drm/doc: Custom Kconfig for KUnit is no longer needed Michał Winiarski
2022-09-06  1:37 ` Bagas Sanjaya
2022-09-06  8:12   ` Michał Winiarski
2022-09-06  8:53     ` Jonathan Corbet [this message]
2022-09-07 17:12 ` José Expósito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8q09943.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@linux.ie \
    --cc=bagasdotme@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=davidgow@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=jose.exposito89@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox