mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: sfr@canb.auug.org.au, kent.overstreet@linux.dev,
	linux-doc@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Documentation: fs/proc: fix allocinfo title
Date: Tue, 26 Mar 2024 10:16:16 -0700	[thread overview]
Message-ID: <40fcf36e-3a60-474e-a7ef-1de874743828@infradead.org> (raw)
In-Reply-To: <20240326073813.727090-1-surenb@google.com>



On 3/26/24 00:38, Suren Baghdasaryan wrote:
> Fix "Title underline too short." warning in the documentation.
> 
> Fixes: d08b311b6d49 ("lib: add allocation tagging support for memory allocation profiling")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> Cc: Randy Dunlap <rdunlap@infradead.org>


Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  Documentation/filesystems/proc.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 5d2fc58b5b1f..245269dd6e02 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -955,7 +955,7 @@ reclaimed to achieve this.
>  
>  
>  allocinfo
> -~~~~~~~
> +~~~~~~~~~
>  
>  Provides information about memory allocations at all locations in the code
>  base. Each allocation in the code is identified by its source file, line

-- 
#Randy

      reply	other threads:[~2024-03-26 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  7:38 Suren Baghdasaryan
2024-03-26 17:16 ` Randy Dunlap [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=40fcf36e-3a60-474e-a7ef-1de874743828@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=surenb@google.com \
    /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

all inboxes | Powered by JetHome®