linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zenghui Yu <zenghui.yu@linux.dev>
To: Chang Yu <marcus.yu.56@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	corbet@lwn.net, pbonzini@redhat.com, linux-doc@vger.kernel.org,
	chang.yu.56@protonmail.com
Subject: Re: [PATCH] Fix "WARNING: Title underline too short."
Date: Wed, 24 Jul 2024 00:18:01 +0800	[thread overview]
Message-ID: <15b15e5d-2db0-4f34-80b3-1b83571f8cb4@linux.dev> (raw)
In-Reply-To: <b9e7e293-38dc-472c-9d53-5dfec5dc4a28@linuxfoundation.org>

On 2024/7/23 23:53, Shuah Khan wrote:
> On 7/22/24 22:29, Chang Yu wrote:
> > Fix "Title underline too short" warning by extending the title line.
> 
> Please specify the subsystem this patch is intended for
> in the summary - also check the correct format for the
> summary in the submbitting patches document - you can
> refer to other commits for the same file in "git log"
> output.
> 
> example:
> 
> [PATCH] doc/kvm: Fix underline too short warning
> 
> Include the warning in the changelog

And it'd be good to always CC all the lists that get_maintainer.pl tells
you, i.e., the KVM list and LKML, even though this is a trivial change.

% ./scripts/get_maintainer.pl Documentation/virt/kvm/api.rst
Paolo Bonzini <pbonzini@redhat.com> (supporter:KERNEL VIRTUAL MACHINE (KVM))
Jonathan Corbet <corbet@lwn.net> (maintainer:DOCUMENTATION)
kvm@vger.kernel.org (open list:KERNEL VIRTUAL MACHINE (KVM))
linux-doc@vger.kernel.org (open list:DOCUMENTATION)
linux-kernel@vger.kernel.org (open list)

Thanks,
Zenghui

      reply	other threads:[~2024-07-23 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23  4:29 [PATCH] Fix "WARNING: Title underline too short." Chang Yu
2024-07-23 15:53 ` Shuah Khan
2024-07-23 16:18   ` Zenghui Yu [this message]

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=15b15e5d-2db0-4f34-80b3-1b83571f8cb4@linux.dev \
    --to=zenghui.yu@linux.dev \
    --cc=chang.yu.56@protonmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=marcus.yu.56@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=skhan@linuxfoundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).