All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: KT Liao <kt.liao@emc.com.tw>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	phoenix@emc.com.tw
Subject: Re: [PATCH] Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB Add 2 ACPI IC ELAN0609, ELAN060B in the ACPI mapping table Signed-off-by: KT Liao <kt.liao@emc.com.tw>
Date: Mon, 14 Aug 2017 20:18:15 -0700	[thread overview]
Message-ID: <20170815031815.GA31856@dtor-ws> (raw)
In-Reply-To: <1502435404-20549-1-git-send-email-kt.liao@emc.com.tw>

On Fri, Aug 11, 2017 at 03:10:04PM +0800, KT Liao wrote:

Applied, however please make sure that there is a blank line in your
commit messages between the first line (subject) and the subsequent
lines comprising the patch description: it will allow the tools work
properly and not create emails with subjects consisting of your entire
commit message.

> ---
>  drivers/input/mouse/elan_i2c_core.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/input/mouse/elan_i2c_core.c b/drivers/input/mouse/elan_i2c_core.c
> index 3b616cb..0d111322 100644
> --- a/drivers/input/mouse/elan_i2c_core.c
> +++ b/drivers/input/mouse/elan_i2c_core.c
> @@ -1248,6 +1248,8 @@ static const struct acpi_device_id elan_acpi_id[] = {
>  	{ "ELAN0100", 0 },
>  	{ "ELAN0600", 0 },
>  	{ "ELAN0605", 0 },
> +	{ "ELAN0609", 0 },
> +	{ "ELAN060B", 0 },
>  	{ "ELAN1000", 0 },
>  	{ }
>  };
> -- 
> 2.7.4
> 

Thanks.

-- 
Dmitry

      reply	other threads:[~2017-08-15  3:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  7:10 [PATCH] Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB Add 2 ACPI IC ELAN0609, ELAN060B in the ACPI mapping table Signed-off-by: KT Liao <kt.liao@emc.com.tw> KT Liao
2017-08-15  3:18 ` Dmitry Torokhov [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=20170815031815.GA31856@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=kt.liao@emc.com.tw \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phoenix@emc.com.tw \
    /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.