linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thomas Gleixner <tglx@linutronix.de>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Borislav Petkov <bp@suse.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] Documentation: maintainer-tip: Rectify link to "Describe your changes" section of submitting-patches.rst
Date: Thu, 23 Mar 2023 11:26:41 -0600	[thread overview]
Message-ID: <87fs9vcram.fsf@meer.lwn.net> (raw)
In-Reply-To: <874jqd9jol.ffs@tglx>

Thomas Gleixner <tglx@linutronix.de> writes:

> On Mon, Mar 20 2023 at 19:43, Bagas Sanjaya wrote:
>> The general changelog rules for the tip tree refers to "Describe your
>> changes" section of submitting patches guide. However, the internal link
>> reference targets to non-existent "submittingpatches" label, which
>> brings reader to the top of the linked doc.
>>
>> Correct the target. No changes to submitting-patches.rst since the
>> required label is already there.
>>
>> Fixes: 31c9d7c8297558 ("Documentation/process: Add tip tree handbook")
>> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>
> In cass Jonathan is picking this up:
>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

I've applied it, thanks.

jon

      reply	other threads:[~2023-03-23 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 12:43 [PATCH] Documentation: maintainer-tip: Rectify link to "Describe your changes" section of submitting-patches.rst Bagas Sanjaya
2023-03-22 10:14 ` Thomas Gleixner
2023-03-23 17:26   ` Jonathan Corbet [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=87fs9vcram.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).