All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Tom Rix <trix@redhat.com>
Cc: Robert Moore <robert.moore@intel.com>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>,
	Len Brown <lenb@kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"open list:ACPI COMPONENT ARCHITECTURE (ACPICA)"
	<devel@acpica.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPICA: cleanup double word in comment
Date: Mon, 31 Jan 2022 19:51:00 +0100	[thread overview]
Message-ID: <CAJZ5v0g5Xxd9kBPUdsC6D4fVHfZafKiGgkTONo2mpqvfgoFDgw@mail.gmail.com> (raw)
In-Reply-To: <20220131133337.1556355-1-trix@redhat.com>

On Mon, Jan 31, 2022 at 2:33 PM <trix@redhat.com> wrote:
>
> From: Tom Rix <trix@redhat.com>
>
> Remove the second 'know'.
>
> Signed-off-by: Tom Rix <trix@redhat.com>

This is ACPICA material, so it needs to be submitted to the upstream
project via https://github.com/acpica/acpica/

Also, it would be good to combine all of the analogous changes in one patch.

> ---
>  drivers/acpi/acpica/exfldio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/acpica/exfldio.c b/drivers/acpi/acpica/exfldio.c
> index bdc7a30d1217c..b92605df3872c 100644
> --- a/drivers/acpi/acpica/exfldio.c
> +++ b/drivers/acpi/acpica/exfldio.c
> @@ -104,7 +104,7 @@ acpi_ex_setup_region(union acpi_operand_object *obj_desc,
>  #ifdef ACPI_UNDER_DEVELOPMENT
>         /*
>          * If the Field access is any_acc, we can now compute the optimal
> -        * access (because we know know the length of the parent region)
> +        * access (because we know the length of the parent region)
>          */
>         if (!(obj_desc->common.flags & AOPOBJ_DATA_VALID)) {
>                 if (ACPI_FAILURE(status)) {
> --
> 2.26.3
>

WARNING: multiple messages have this Message-ID (diff)
From: Rafael J. Wysocki <rafael at kernel.org>
To: devel@acpica.org
Subject: [Devel] Re: [PATCH] ACPICA: cleanup double word in comment
Date: Mon, 31 Jan 2022 19:51:00 +0100	[thread overview]
Message-ID: <CAJZ5v0g5Xxd9kBPUdsC6D4fVHfZafKiGgkTONo2mpqvfgoFDgw@mail.gmail.com> (raw)
In-Reply-To: 20220131133337.1556355-1-trix@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Mon, Jan 31, 2022 at 2:33 PM <trix(a)redhat.com> wrote:
>
> From: Tom Rix <trix(a)redhat.com>
>
> Remove the second 'know'.
>
> Signed-off-by: Tom Rix <trix(a)redhat.com>

This is ACPICA material, so it needs to be submitted to the upstream
project via https://github.com/acpica/acpica/

Also, it would be good to combine all of the analogous changes in one patch.

> ---
>  drivers/acpi/acpica/exfldio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/acpica/exfldio.c b/drivers/acpi/acpica/exfldio.c
> index bdc7a30d1217c..b92605df3872c 100644
> --- a/drivers/acpi/acpica/exfldio.c
> +++ b/drivers/acpi/acpica/exfldio.c
> @@ -104,7 +104,7 @@ acpi_ex_setup_region(union acpi_operand_object *obj_desc,
>  #ifdef ACPI_UNDER_DEVELOPMENT
>         /*
>          * If the Field access is any_acc, we can now compute the optimal
> -        * access (because we know know the length of the parent region)
> +        * access (because we know the length of the parent region)
>          */
>         if (!(obj_desc->common.flags & AOPOBJ_DATA_VALID)) {
>                 if (ACPI_FAILURE(status)) {
> --
> 2.26.3
>

  reply	other threads:[~2022-01-31 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 13:33 [PATCH] ACPICA: cleanup double word in comment trix
2022-01-31 18:51 ` Rafael J. Wysocki [this message]
2022-01-31 18:51   ` [Devel] " Rafael J. Wysocki
2022-01-31 20:18   ` Tom Rix
  -- strict thread matches above, loose matches on Subject: below --
2022-01-30 14:59 trix

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=CAJZ5v0g5Xxd9kBPUdsC6D4fVHfZafKiGgkTONo2mpqvfgoFDgw@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=devel@acpica.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.com \
    --cc=trix@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.