From: Al Stone <ahs3@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ACPI / LPSS: change 'does not have' to 'has' in comment
Date: Tue, 22 Dec 2015 13:04:31 -0700 [thread overview]
Message-ID: <5679ACCF.1000608@redhat.com> (raw)
In-Reply-To: <1450729869-115532-1-git-send-email-andriy.shevchenko@linux.intel.com>
On 12/21/2015 01:31 PM, Andy Shevchenko wrote:
> The LPSS DMA device has neither _PS0 nor _PS3 method. Fix the wording in
> the comment line.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/acpi/acpi_lpss.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/acpi_lpss.c b/drivers/acpi/acpi_lpss.c
> index 84d3d90..047281a6 100644
> --- a/drivers/acpi/acpi_lpss.c
> +++ b/drivers/acpi/acpi_lpss.c
> @@ -95,7 +95,7 @@ static unsigned int lpss_quirks;
> /*
> * LPSS_QUIRK_ALWAYS_POWER_ON: override power state for LPSS DMA device.
> *
> - * The LPSS DMA controller does not have neither _PS0 nor _PS3 method. Moreover
> + * The LPSS DMA controller has neither _PS0 nor _PS3 method. Moreover
> * it can be powered off automatically whenever the last LPSS device goes down.
> * In case of no power any access to the DMA controller will hang the system.
> * The behaviour is reproduced on some HP laptops based on Intel BayTrail as
>
Much better :). Thanks for the quick turnaround, Andy.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
prev parent reply other threads:[~2015-12-22 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 20:31 [PATCH v2 1/1] ACPI / LPSS: change 'does not have' to 'has' in comment Andy Shevchenko
2015-12-22 20:04 ` Al Stone [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=5679ACCF.1000608@redhat.com \
--to=ahs3@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.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;
as well as URLs for NNTP newsgroup(s).