All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT] Pull request: u-boot-dfu (06.11.2019)
Date: Thu, 7 Nov 2019 00:26:32 +0100	[thread overview]
Message-ID: <680af953-bcd1-fb8d-04f3-b8c09ac5e575@denx.de> (raw)
In-Reply-To: <20191106132718.7c59df31@jawa>

On 11/6/19 1:27 PM, Lukasz Majewski wrote:
> Hi Marek,
Hi,

>> On 11/6/19 12:27 PM, Lukasz Majewski wrote:
>>> Hi Marek,
>>>   
>>>> On 11/6/19 10:21 AM, Lukasz Majewski wrote:  
>>>>> Dear Marek,
>>>>>
>>>>> The following changes since commit
>>>>> 14d39c9e1dc9397febd58399a70f32e7481bbc27:
>>>>>
>>>>>   travis: Rework how we write the ~/.buildman file (2019-11-05
>>>>> 10:44:16 -0500)
>>>>>
>>>>> are available in the Git repository at:
>>>>>
>>>>>   git at gitlab.denx.de:u-boot/custodians/u-boot-dfu.git 
>>>>>
>>>>> BRANCH: master
>>>>> https://gitlab.denx.de/u-boot/custodians/u-boot-dfu/commits/master
>>>>>
>>>>> Merge TAG:
>>>>> https://gitlab.denx.de/u-boot/custodians/u-boot-dfu/-/tags/u-boot-dfu-06Nov2019
>>>>>
>>>>> for you to fetch changes up to
>>>>> 8c5df588e89b2bf4aad4c95b17cfc8634b8dcaaf:
>>>>>
>>>>>   usb: composite: add BOS descriptor support to composite
>>>>> framework (2019-11-06 01:01:06 +0100)
>>>>>
>>>>>
>>>>> My remark:
>>>>>
>>>>> - Those patches are new code, (like adding the USB 3.0 controller
>>>>> from Cadence) hence IMHO it would be best to add them to your next
>>>>> PR    
>>>>
>>>> We are already in -rc cycle, so fixes only. Should this PR be for
>>>> -next ?
>>>>  
>>>
>>> The BOS support is a fix do SS USB.
>>>
>>> And the Cadence USB support is a new code, which is not touching any
>>> relevant parts of USB (and IMHO it applies to the same category as
>>> adding new boards outside the merge window).
>>>
>>> However, if you believe that this code is not eligible for
>>> u-boot-usb/master ,then yes please pull it into -next.  
>>
>> That decision is up to you. If you think this is safe to pull in RC1,
>> I don't mind either way.
> 
> Ok. Lets then pull it in RC1. Thanks for understanding :-)

Pulled, thanks.

      reply	other threads:[~2019-11-06 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06  9:21 [U-Boot] [GIT] Pull request: u-boot-dfu (06.11.2019) Lukasz Majewski
2019-11-06 10:49 ` Marek Vasut
2019-11-06 11:27   ` Lukasz Majewski
2019-11-06 11:32     ` Marek Vasut
2019-11-06 12:27       ` Lukasz Majewski
2019-11-06 23:26         ` Marek Vasut [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=680af953-bcd1-fb8d-04f3-b8c09ac5e575@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.