Hi,
Am 07.03.2016 um 08:26 schrieb Felipe Balbi :
>
> Hi,
>
> John Youn writes:
>> [ text/plain ]
>> On 3/4/2016 6:14 PM, Doug Anderson wrote:
>>> Hi,
>>>
>>> On Fri, Mar 4, 2016 at 5:56 PM, John Youn wrote:
On 3/4/2016
Hi,
John Youn writes:
> [ text/plain ]
> On 3/4/2016 6:14 PM, Doug Anderson wrote:
>> Hi,
>>
>> On Fri, Mar 4, 2016 at 5:56 PM, John Youn wrote:
>>> On 3/4/2016 5:04 PM, Doug Anderson wrote:
Felipe,
Michael pointed out that
On 3/4/2016 6:14 PM, Doug Anderson wrote:
> Hi,
>
> On Fri, Mar 4, 2016 at 5:56 PM, John Youn wrote:
>> On 3/4/2016 5:04 PM, Doug Anderson wrote:
>>> Felipe,
>>>
>>> Michael pointed out that there's an odd merge that happened.
>>> Specifically it looks like commit
Hi,
On Fri, Mar 4, 2016 at 5:56 PM, John Youn wrote:
> On 3/4/2016 5:04 PM, Doug Anderson wrote:
>> Felipe,
>>
>> Michael pointed out that there's an odd merge that happened.
>> Specifically it looks like commit bd84f4ae9986 ("usb: dwc2: Add extra
>> delay when forcing
On 3/4/2016 5:04 PM, Doug Anderson wrote:
> Felipe,
>
> Michael pointed out that there's an odd merge that happened.
> Specifically it looks like commit bd84f4ae9986 ("usb: dwc2: Add extra
> delay when forcing dr_mode") got lost somehow in the merge commit
> 3b30be3b6487 ("Merge tag 'v4.5-rc6'
Felipe,
Michael pointed out that there's an odd merge that happened.
Specifically it looks like commit bd84f4ae9986 ("usb: dwc2: Add extra
delay when forcing dr_mode") got lost somehow in the merge commit
3b30be3b6487 ("Merge tag 'v4.5-rc6' into next")
Specifically:
$ git blame 3b30be3b6487 --