public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, andrii@kernel.org,
	linux-kernel-mentees@lists.linux.dev, shuah@kernel.org,
	tj@kernel.org, kernel-team@meta.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next] docs: bpf: fix bullet point formatting warning
Date: Tue, 13 May 2025 16:10:28 +0000	[thread overview]
Message-ID: <174715262801.1715489.17129474183914468130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250513015901.475207-1-khaledelnaggarlinux@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Tue, 13 May 2025 04:58:59 +0300 you wrote:
> Fix indentation for a bullet list item in bpf_iterators.rst.
> According to reStructuredText rules, bullet list item bodies must be
> consistently indented relative to the bullet. The indentation of the
> first line after the bullet determines the alignment for the rest of
> the item body.
> 
> Reported by smatch:
>   /linux/Documentation/bpf/bpf_iterators.rst:55: WARNING: Bullet list ends without a blank line; unexpected unindent. [docutils]
> 
> [...]

Here is the summary with links:
  - [bpf-next] docs: bpf: fix bullet point formatting warning
    https://git.kernel.org/bpf/bpf-next/c/79af71c5fe44

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-05-13 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13  1:58 [PATCH bpf-next] docs: bpf: fix bullet point formatting warning Khaled Elnaggar
2025-05-13 16:05 ` Andrii Nakryiko
2025-05-13 16:10 ` patchwork-bot+netdevbpf [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=174715262801.1715489.17129474183914468130.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=khaledelnaggarlinux@gmail.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=shuah@kernel.org \
    --cc=tj@kernel.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