From: Guenter Roeck <groeck@google.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Guenter Roeck <groeck@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
kernel@collabora.com, Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH v2 11/12] platform/chrome: cros_ec_lightbar: remove pr_fmt() define
Date: Mon, 28 Jan 2019 11:36:22 -0800 [thread overview]
Message-ID: <CABXOdTdcmW+VciVP_t8aa64m=_KS0zMsbObpSMpi9eWZ8_NvMw@mail.gmail.com> (raw)
In-Reply-To: <20190126095131.4756-12-enric.balletbo@collabora.com>
On Sat, Jan 26, 2019 at 1:51 AM Enric Balletbo i Serra
<enric.balletbo@collabora.com> wrote:
>
> This driver no longer has any pr_{level} messages. Remove the pr_fmt().
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
> ---
>
> Changes in v2: None
>
> drivers/platform/chrome/cros_ec_lightbar.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/platform/chrome/cros_ec_lightbar.c b/drivers/platform/chrome/cros_ec_lightbar.c
> index 37689ad79544..d30a6650b0b5 100644
> --- a/drivers/platform/chrome/cros_ec_lightbar.c
> +++ b/drivers/platform/chrome/cros_ec_lightbar.c
> @@ -3,8 +3,6 @@
> //
> // Copyright (C) 2014 Google, Inc.
>
> -#define pr_fmt(fmt) "cros_ec_lightbar: " fmt
> -
> #include <linux/ctype.h>
> #include <linux/delay.h>
> #include <linux/device.h>
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-01-28 19:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 9:51 [PATCH v2 00/12] platform/chrome: switch to SPDX license and some minor cleanup Enric Balletbo i Serra
2019-01-26 9:51 ` [PATCH v2 01/12] platform/chrome: cromeos_pstore: switch to SPDX identifier Enric Balletbo i Serra
2019-01-28 19:28 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 02/12] platform/chrome: cros_ec_debugfs: " Enric Balletbo i Serra
2019-01-28 19:28 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 03/12] platform/chrome: cros_ec_lightbar: " Enric Balletbo i Serra
2019-01-28 19:29 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 04/12] platform/chrome: cros_ec_sysfs: " Enric Balletbo i Serra
2019-01-28 19:29 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 05/12] platform/chrome: cros_ec_vbc: " Enric Balletbo i Serra
2019-01-28 19:30 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 06/12] platform/chrome: cros_ec_i2c: " Enric Balletbo i Serra
2019-01-28 19:31 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 07/12] platform/chrome: cros_ec_lpc: " Enric Balletbo i Serra
2019-01-28 19:33 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 08/12] platform/chrome: cros_ec_proto: " Enric Balletbo i Serra
2019-01-28 19:33 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 09/12] platform/chrome: cros_ec_spi: " Enric Balletbo i Serra
2019-01-28 19:34 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 10/12] platform/chrome: cros_kbd_led_backlight: " Enric Balletbo i Serra
2019-01-28 19:35 ` Guenter Roeck
2019-01-26 9:51 ` [PATCH v2 11/12] platform/chrome: cros_ec_lightbar: remove pr_fmt() define Enric Balletbo i Serra
2019-01-28 19:36 ` Guenter Roeck [this message]
2019-01-26 9:51 ` [PATCH v2 12/12] platform/chrome: cros_ec_sysfs: " Enric Balletbo i Serra
2019-01-28 19:36 ` Guenter Roeck
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='CABXOdTdcmW+VciVP_t8aa64m=_KS0zMsbObpSMpi9eWZ8_NvMw@mail.gmail.com' \
--to=groeck@google.com \
--cc=bleung@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;
as well as URLs for NNTP newsgroup(s).