From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Gianfranco Costamagna <locutusofborg@debian.org>
Cc: Antonio Rosario Intilisano <antonio.intilisano@gmail.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
"vger@kernel.org" <vger@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Chiu <chiu@endlessm.com>, Daniel Drake <drake@endlessm.com>
Subject: Re: [PATCH] platform/x86: acer-wmi: add another KEY_POWER keycode
Date: Tue, 24 Apr 2018 20:02:35 +0300 [thread overview]
Message-ID: <1524589355.21176.507.camel@linux.intel.com> (raw)
In-Reply-To: <CAHp75VeDhyKmcJqA5paqJEPsw-gpzq7iJee+zu=ZMqUpDv0_6A@mail.gmail.com>
On Tue, 2018-04-24 at 19:15 +0300, Andy Shevchenko wrote:
> On Mon, Apr 23, 2018 at 5:48 PM, Gianfranco Costamagna
> <locutusofborg@debian.org> wrote:
> > Hello,
> >
> > > Can you give your corresponding tag as well?
> >
> >
> > we are implementing the fix right now, please follow bug
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766054
>
> OK, I postpone this patch until new version.
Or I missed the point and it's working? Tell me what to do with it.
For now I pushed to my review and testing queue, thanks!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-04-24 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 21:26 [PATCH] platform/x86: acer-wmi: add another KEY_POWER keycode Antonio Rosario Intilisano
2018-04-21 18:40 ` Gianfranco Costamagna
2018-04-23 14:06 ` Andy Shevchenko
2018-04-23 14:48 ` Gianfranco Costamagna
2018-04-24 16:15 ` Andy Shevchenko
2018-04-24 17:02 ` Andy Shevchenko [this message]
2018-04-24 18:23 ` Gianfranco Costamagna
2018-04-24 18:33 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2018-04-20 21:32 Antonio Rosario Intilisano
2018-04-27 21:50 Antonio Rosario Intilisano
2018-05-07 14:08 ` Andy Shevchenko
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=1524589355.21176.507.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=antonio.intilisano@gmail.com \
--cc=chiu@endlessm.com \
--cc=drake@endlessm.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=locutusofborg@debian.org \
--cc=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