HI,
On 05-02-18 00:28, Chanwoo Choi wrote:
On 2018년 02월 02일 17:10, Hans de Goede wrote:
Hi,
On 02-02-18 01:32, Chanwoo Choi wrote:
On 2018년 01월 26일 04:39, Hans de Goede wrote:
Some other drivers may be waiting for our extcon to show-up (exiting their
probe methods with -EPROBE_DEFER until
HI,
On 05-02-18 00:28, Chanwoo Choi wrote:
On 2018년 02월 02일 17:10, Hans de Goede wrote:
Hi,
On 02-02-18 01:32, Chanwoo Choi wrote:
On 2018년 01월 26일 04:39, Hans de Goede wrote:
Some other drivers may be waiting for our extcon to show-up (exiting their
probe methods with -EPROBE_DEFER until
On 2018년 02월 02일 17:10, Hans de Goede wrote:
> Hi,
>
> On 02-02-18 01:32, Chanwoo Choi wrote:
>> On 2018년 01월 26일 04:39, 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
On 2018년 02월 02일 17:10, Hans de Goede wrote:
> Hi,
>
> On 02-02-18 01:32, Chanwoo Choi wrote:
>> On 2018년 01월 26일 04:39, 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
Hi,
On 02-02-18 01:32, Chanwoo Choi wrote:
On 2018년 01월 26일 04:39, 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
Hi,
On 02-02-18 01:32, Chanwoo Choi wrote:
On 2018년 01월 26일 04:39, 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
On 2018년 01월 26일 04:39, 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
On 2018년 01월 26일 04:39, 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
On 2018년 01월 26일 04:39, 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
On 2018년 01월 26일 04:39, 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
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
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
12 matches
Mail list logo
