From: patchwork-bot+chrome-platform@kernel.org
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev, robbarnes@google.com,
evgreen@chromium.org
Subject: Re: [PATCH 0/4] platform/chrome: fix kernel-doc warnings
Date: Fri, 13 Jan 2023 21:20:55 +0000 [thread overview]
Message-ID: <167364485579.21086.10146696175738479548.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230111055728.708990-1-tzungbi@kernel.org>
Hello:
This series was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Wed, 11 Jan 2023 13:57:24 +0800 you wrote:
> The series fixes kernel-doc warnings in various places.
>
> All of them can be squashed into 1 fix actually. However, I think it would
> be more clear to separate the first 2 commits as the patches introduced
> the warnings are quite new.
>
> For the 3rd patch, I am not sure if it makes sense to have the Fixes tag.
> It is a little bit old (~2019).
>
> [...]
Here is the summary with links:
- [1/4] platform/chrome: fix kernel-doc warnings for panic notifier
https://git.kernel.org/chrome-platform/c/16d73129f1fd
- [2/4] platform/chrome: fix kernel-doc warning for suspend_timeout_ms
https://git.kernel.org/chrome-platform/c/20eb556dac27
- [3/4] platform/chrome: fix kernel-doc warning for last_resume_result
https://git.kernel.org/chrome-platform/c/212c9b9c395f
- [4/4] platform/chrome: fix kernel-doc warnings for cros_ec_command
https://git.kernel.org/chrome-platform/c/5fa1dd818fb4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-13 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 5:57 [PATCH 0/4] platform/chrome: fix kernel-doc warnings Tzung-Bi Shih
2023-01-11 5:57 ` [PATCH 1/4] platform/chrome: fix kernel-doc warnings for panic notifier Tzung-Bi Shih
2023-01-11 16:30 ` Guenter Roeck
2023-01-11 5:57 ` [PATCH 2/4] platform/chrome: fix kernel-doc warning for suspend_timeout_ms Tzung-Bi Shih
2023-01-11 16:31 ` Guenter Roeck
2023-01-11 5:57 ` [PATCH 3/4] platform/chrome: fix kernel-doc warning for last_resume_result Tzung-Bi Shih
2023-01-11 16:31 ` Guenter Roeck
2023-01-11 5:57 ` [PATCH 4/4] platform/chrome: fix kernel-doc warnings for cros_ec_command Tzung-Bi Shih
2023-01-11 16:32 ` Guenter Roeck
2023-01-13 21:20 ` patchwork-bot+chrome-platform [this message]
2023-01-15 12:50 ` [PATCH 0/4] platform/chrome: fix kernel-doc warnings patchwork-bot+chrome-platform
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=167364485579.21086.10146696175738479548.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=evgreen@chromium.org \
--cc=groeck@chromium.org \
--cc=robbarnes@google.com \
--cc=tzungbi@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 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.