linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Hans de Goede <hdegoede@redhat.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] extcon: int3496: process id-pin first so that we start with the right status
Date: Mon, 12 Feb 2018 08:41:11 +0900	[thread overview]
Message-ID: <5A80D497.80202@samsung.com> (raw)
In-Reply-To: <5A796400.20905@samsung.com>

On 2018년 02월 06일 17:14, Chanwoo Choi wrote:
> On 2018년 02월 06일 17:10, Hans de Goede wrote:
>> Some other drivers may be waiting for our extcon to show-up (exiting their
>> probe methods with -EPROBE_DEFER until we show up).
>>
>> These drivers will typically get the cable state directly after getting
>> the extcon, this commit changes the int3496 code to process the id-pin
>> before registering the extcon, so that other drivers see the correct state
>> right away.
>>
>> Fixes: 2f556bdb9f2e ("extcon: int3496: Add Intel INT3496 ACPI ... driver")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>>  drivers/extcon/extcon-intel-int3496.c | 7 ++++---
>>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> Applied it. Thanks.
> 

This patch had the bug reported by Hans.
Please ignore what I applied patch.
I don't apply it and I'll wait v3 patch.

-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      reply	other threads:[~2018-02-11 23:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180206081056epcas2p19485991e157843cf2e016a6dfed41027@epcas2p1.samsung.com>
2018-02-06  8:10 ` [PATCH v2] extcon: int3496: process id-pin first so that we start with the right status Hans de Goede
2018-02-06  8:14   ` Chanwoo Choi
2018-02-11 23:41     ` Chanwoo Choi [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=5A80D497.80202@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).