From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, Benson Leung <bleung@google.com>,
Guenter Roeck <groeck@chromium.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Documentation update for Chrome OS ACPI
Date: Wed, 18 May 2022 19:56:50 +0800 [thread overview]
Message-ID: <YoTfArGLd85jaG2Y@google.com> (raw)
In-Reply-To: <20220518083524.37380-1-bagasdotme@gmail.com>
On Wed, May 18, 2022 at 03:35:22PM +0700, Bagas Sanjaya wrote:
> Two documentation patches touching Chrome OS ACPI sysfs.
>
> 1. Patch [1/2] fixes htmldocs warning reported in linux-next and should
> be merged before upcoming merge window.
> 2. Patch [2/2] rewrites symbol descriptions to use imperative mood. It
> can be merged when appropriate, independent of previous patch
> above.
>
> [...]
Applied, thanks!
[1/2] platform/chrome: Use tables for values lists of ChromeOS ACPI sysfs ABI
commit: 596cbc6ab0abd18206b3247aaeaa225788afaf8c
[2/2] platform/chrome: Use imperative mood for ChromeOS ACPI sysfs ABI descriptions
commit: 7bff62406671dd89e9d1a7bf00169197f2833c41
prev parent reply other threads:[~2022-05-18 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 8:35 [PATCH v2 0/2] Documentation update for Chrome OS ACPI Bagas Sanjaya
2022-05-18 8:35 ` [PATCH v2 1/2] platform/chrome: Use tables for values lists of ChromeOS ACPI sysfs ABI Bagas Sanjaya
2022-05-18 11:27 ` Muhammad Usama Anjum
2022-05-18 8:35 ` [PATCH v2 2/2] platform/chrome: Use imperative mood for ChromeOS ACPI sysfs ABI descriptions Bagas Sanjaya
2022-05-18 11:27 ` Muhammad Usama Anjum
2022-05-18 11:56 ` Tzung-Bi Shih [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=YoTfArGLd85jaG2Y@google.com \
--to=tzungbi@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=usama.anjum@collabora.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).