linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Xiaofei Tan <tanxiaofei@huawei.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, "Zhang, Rui" <rui.zhang@intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>,
	linuxarm@openeuler.org
Subject: Re: [PATCH v3 00/12] acpi: fix some coding style issues
Date: Mon, 29 Mar 2021 14:50:08 +0200	[thread overview]
Message-ID: <CAJZ5v0i=RPyvWfVuGQ0nWf_0QRw70=qZd6j85CTPWaaWPa_5KQ@mail.gmail.com> (raw)
In-Reply-To: <1616846904-25719-1-git-send-email-tanxiaofei@huawei.com>

On Sat, Mar 27, 2021 at 1:11 PM Xiaofei Tan <tanxiaofei@huawei.com> wrote:
>
> Fix some coding style issues reported by checkpatch.pl.
> Only cleanup and no function changes.
>
> Differences from v2 to v3:
> - Remove the modifications that may cause function change.
>
> Differences from v1 to v2:
> - Add subsystem and module name in the name of patch 05/15.
> - Change to use more proper module name for some patch names.
>
> Xiaofei Tan (12):
>   ACPI: APD: fix a block comment align issue
>   ACPI: processor: fix some coding style issues
>   ACPI: ipmi: remove useless return statement for void function
>   ACPI: LPSS: add a missed blank line after declarations
>   ACPI: acpi_pad: add a missed blank line after declarations
>   ACPI: battery: fix some coding style issues
>   ACPI: button: fix some coding style issues
>   ACPI: CPPC: fix some coding style issues
>   ACPI: custom_method: fix a coding style issue
>   ACPI: PM: add a missed blank line after declarations
>   ACPI: sysfs: fix some coding style issues
>   ACPI: dock: fix some coding style issues
>
>  drivers/acpi/acpi_apd.c       |  8 ++---
>  drivers/acpi/acpi_ipmi.c      |  1 -
>  drivers/acpi/acpi_lpss.c      |  2 ++
>  drivers/acpi/acpi_pad.c       |  4 +++
>  drivers/acpi/acpi_processor.c | 18 +++--------
>  drivers/acpi/battery.c        | 63 ++++++++++++++++++++------------------
>  drivers/acpi/button.c         |  9 ++----
>  drivers/acpi/cppc_acpi.c      | 71 ++++++++++++++++++++++---------------------
>  drivers/acpi/custom_method.c  |  2 +-
>  drivers/acpi/device_pm.c      |  3 ++
>  drivers/acpi/device_sysfs.c   | 15 ++++++---
>  drivers/acpi/dock.c           |  7 +++--
>  12 files changed, 106 insertions(+), 97 deletions(-)
>
> --

Can you please stop sending new versions of this for a while?

You've sent three of them over the last weekend and honestly I haven't
had a chance to look at the first one even.

  parent reply	other threads:[~2021-03-29 12:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 12:08 [PATCH v3 00/12] acpi: fix some coding style issues Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 01/12] ACPI: APD: fix a block comment align issue Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 02/12] ACPI: processor: fix some coding style issues Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 03/12] ACPI: ipmi: remove useless return statement for void function Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 04/12] ACPI: LPSS: add a missed blank line after declarations Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 05/12] ACPI: acpi_pad: " Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 06/12] ACPI: battery: fix some coding style issues Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 07/12] ACPI: button: " Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 08/12] ACPI: CPPC: " Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 09/12] ACPI: custom_method: fix a coding style issue Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 10/12] ACPI: PM: add a missed blank line after declarations Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 11/12] ACPI: sysfs: fix some coding style issues Xiaofei Tan
2021-03-27 12:08 ` [PATCH v3 12/12] ACPI: dock: " Xiaofei Tan
2021-03-29 12:50 ` Rafael J. Wysocki [this message]
2021-03-29 13:37   ` [Linuxarm] Re: [PATCH v3 00/12] acpi: " Xiaofei Tan
2021-04-08 14:28 ` Rafael J. Wysocki

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='CAJZ5v0i=RPyvWfVuGQ0nWf_0QRw70=qZd6j85CTPWaaWPa_5KQ@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=tanxiaofei@huawei.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).