From: Benson Leung <bleung@google.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org,
Collabora Kernel ML <kernel@collabora.com>,
groeck@chromium.org, bleung@chromium.org, dtor@chromium.org,
gwendal@chromium.org
Subject: Re: [PATCH] platform/chrome: cros_ec_i2c: Appease the kernel-doc deity
Date: Mon, 4 May 2020 13:59:20 -0700 [thread overview]
Message-ID: <20200504205920.GA102727@google.com> (raw)
In-Reply-To: <20200414201313.1507146-1-enric.balletbo@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Hi Enric,
On Tue, Apr 14, 2020 at 10:13:13PM +0200, Enric Balletbo i Serra wrote:
> Replace a comment starting with /** by simply /* to avoid having
> it interpreted as a kernel-doc comment.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Applied for chrome-platform-5.8. You'll find it in the for-kernelci branch
very shortly.
Thanks,
Benson
> ---
>
> drivers/platform/chrome/cros_ec_i2c.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/chrome/cros_ec_i2c.c b/drivers/platform/chrome/cros_ec_i2c.c
> index 6119eccd8a18..30c8938c27d5 100644
> --- a/drivers/platform/chrome/cros_ec_i2c.c
> +++ b/drivers/platform/chrome/cros_ec_i2c.c
> @@ -16,7 +16,7 @@
>
> #include "cros_ec.h"
>
> -/**
> +/*
> * Request format for protocol v3
> * byte 0 0xda (EC_COMMAND_PROTOCOL_3)
> * byte 1-8 struct ec_host_request
> --
> 2.25.1
>
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2020-05-04 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 20:13 [PATCH] platform/chrome: cros_ec_i2c: Appease the kernel-doc deity Enric Balletbo i Serra
2020-05-04 20:59 ` Benson Leung [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=20200504205920.GA102727@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=dtor@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.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