linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Zhang Rui <rui.zhang@intel.com>,
	yao.jin@intel.com, linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] soc_button_array: fix the issue that button device can't be enumerated since 3.16-rc1
Date: Wed, 9 Jul 2014 09:57:32 -0700	[thread overview]
Message-ID: <20140709165732.GD10364@core.coreip.homeip.net> (raw)
In-Reply-To: <2556427.cdnVoQoSXY@vostro.rjw.lan>

On Tue, Jul 08, 2014 at 10:50:04PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, July 02, 2014 10:01:53 PM Zhang Rui wrote:
> > From c2ee1886ba230d9d93d2ea2f350b1dc1a2d5ead5 Mon Sep 17 00:00:00 2001
> > From: Jin Yao <yao.jin@linux.intel.com>
> > Date: Thu, 26 Jun 2014 10:26:44 +0800
> > Subject: [PATCH] soc_button_array: fix the issue that button device can't be
> >  enumerated since 3.16-rc1
> 
> Hi Rui,
> 
> For 3.16 I'm afraid we need to add the missing device ID to the PNP list.
> It is too late to do the conversion at this point IMO and we can do it later.

But for 3.17 this patch is the right way of doing things, right?

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2014-07-09 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1404309504.8366.93.camel@rzhang1-toshiba>
2014-07-02 14:01 ` [PATCH] soc_button_array: fix the issue that button device can't be enumerated since 3.16-rc1 Zhang Rui
2014-07-08 20:50   ` Rafael J. Wysocki
2014-07-09  2:27     ` Zhang Rui
2014-07-09 12:51       ` Rafael J. Wysocki
2014-07-09 16:57     ` Dmitry Torokhov [this message]
2014-07-10  6:24       ` Zhang Rui
2014-07-30  6:45       ` Zhang Rui
2014-09-22  1:44         ` Zhang Rui
2014-09-22 17:36           ` Dmitry Torokhov
2014-09-23  1:05             ` Zhang Rui

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=20140709165732.GD10364@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=yao.jin@intel.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).