From: Benson Leung <bleung@google.com>
To: Colin King <colin.king@canonical.com>
Cc: Benson Leung <bleung@chromium.org>,
Olof Johansson <olof@lixom.net>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: cros_ec_lpc: remove redundant pointer request
Date: Fri, 15 Dec 2017 21:13:50 -0800 [thread overview]
Message-ID: <20171216051350.GC79455@decatoncale.mtv.corp.google.com> (raw)
In-Reply-To: <20171031102747.20154-1-colin.king@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hi Colin,
On Tue, Oct 31, 2017 at 10:27:47AM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Pointer request is being assigned but never used, so remove it. Cleans
> up the clang warning:
>
> drivers/platform/chrome/cros_ec_lpc.c:68:2: warning: Value stored to
> 'request' is never read
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Thanks for the patch. Sorry for the delay. Applied for v4.16.
Thanks,
Benson
> ---
> drivers/platform/chrome/cros_ec_lpc.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/platform/chrome/cros_ec_lpc.c b/drivers/platform/chrome/cros_ec_lpc.c
> index 1baf720faf69..87e9747d229a 100644
> --- a/drivers/platform/chrome/cros_ec_lpc.c
> +++ b/drivers/platform/chrome/cros_ec_lpc.c
> @@ -54,7 +54,6 @@ static int ec_response_timed_out(void)
> static int cros_ec_pkt_xfer_lpc(struct cros_ec_device *ec,
> struct cros_ec_command *msg)
> {
> - struct ec_host_request *request;
> struct ec_host_response response;
> u8 sum;
> int ret = 0;
> @@ -65,8 +64,6 @@ static int cros_ec_pkt_xfer_lpc(struct cros_ec_device *ec,
> /* Write buffer */
> cros_ec_lpc_write_bytes(EC_LPC_ADDR_HOST_PACKET, ret, ec->dout);
>
> - request = (struct ec_host_request *)ec->dout;
> -
> /* Here we go */
> sum = EC_COMMAND_PROTOCOL_3;
> cros_ec_lpc_write_bytes(EC_LPC_ADDR_HOST_CMD, 1, &sum);
> --
> 2.14.1
>
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-12-16 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 10:27 Colin King
2017-12-16 5:13 ` 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=20171216051350.GC79455@decatoncale.mtv.corp.google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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
Powered by JetHome