All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] zsmalloc: make zspage chain size configurable
Date: Fri, 6 Jan 2023 11:40:43 +0900	[thread overview]
Message-ID: <Y7eKK7wKfv6E4NMn@google.com> (raw)
In-Reply-To: <202301060349.wchW6HX9-lkp@intel.com>

On (23/01/06 03:49), kernel test robot wrote:
> All warnings (new ones prefixed by >>):
> 
> >> Documentation/admin-guide/blockdev/zsmalloc.rst:19: WARNING: Literal block expected; none found.
> >> Documentation/admin-guide/blockdev/zsmalloc.rst:21: WARNING: Unexpected indentation.
> >> Documentation/admin-guide/blockdev/zsmalloc.rst:22: WARNING: Block quote ends without a blank line; unexpected unindent.
> >> Documentation/admin-guide/blockdev/zsmalloc.rst: WARNING: document isn't included in any toctree
> 
> vim +19 Documentation/admin-guide/blockdev/zsmalloc.rst
> 
>     18	
>   > 19	class  size almost_full almost_empty obj_allocated   obj_used pages_used pages_per_zspage freeable
>     20	..
>   > 21	   94  1536           0            0             0          0          0                3        0
>   > 22	  100  1632           0            0             0          0          0                2        0
>     23	..
>     24	

Thanks.

OK, added `make htmldocs` to my build scripts, time to get used to
the fact that we now make docs. I fixed all the warnings and moved
the contents to Documentation/mm/zsmalloc.rst file of which I was
not aware before.

Will include all the improvements into v2.

  reply	other threads:[~2023-01-06  2:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  5:35 [PATCH 0/4] zsmalloc: make zspage chain size configurable Sergey Senozhatsky
2023-01-05  5:35 ` [PATCH 1/4] zsmalloc: rework zspage chain size selection Sergey Senozhatsky
2023-01-05  5:35 ` [PATCH 2/4] zsmalloc: skip chain size calculation for pow_of_2 classes Sergey Senozhatsky
2023-01-05  5:35 ` [PATCH 3/4] zsmalloc: make zspage chain size configurable Sergey Senozhatsky
2023-01-05 19:49   ` kernel test robot
2023-01-06  2:40     ` Sergey Senozhatsky [this message]
2023-01-05  5:35 ` [PATCH 4/4] zsmalloc: set default zspage chain size to 8 Sergey Senozhatsky

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=Y7eKK7wKfv6E4NMn@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=minchan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.