From: patchwork-bot+netdevbpf@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, jiri@nvidia.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, vikas.gupta@broadcom.com, gospo@broadcom.com,
lkp@intel.com
Subject: Re: [PATCH net-next] Documentation: devlink: add add devlink-selftests to the table of contents
Date: Mon, 01 Aug 2022 19:30:14 +0000 [thread overview]
Message-ID: <165938221407.30942.11853092153259357010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220730022058.16813-1-bagasdotme@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 30 Jul 2022 09:20:57 +0700 you wrote:
> Commit 08f588fa301bef ("devlink: introduce framework for selftests") adds
> documentation for devlink selftests framework, but it is missing from
> table of contents.
>
> Add it.
>
> Link: https://lore.kernel.org/linux-doc/202207300406.CUBuyN5i-lkp@intel.com/
> Fixes: 08f588fa301bef ("devlink: introduce framework for selftests")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next] Documentation: devlink: add add devlink-selftests to the table of contents
https://git.kernel.org/netdev/net-next/c/4ff7c8fc81ce
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-08-01 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 2:20 [PATCH net-next] Documentation: devlink: add add devlink-selftests to the table of contents Bagas Sanjaya
2022-08-01 19:30 ` 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=165938221407.30942.11853092153259357010.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vikas.gupta@broadcom.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;
as well as URLs for NNTP newsgroup(s).