From: Angus Ainslie <angus@akkea.ca>
To: Marek Vasut <marex@denx.de>
Cc: u-boot@lists.denx.de, sbabic@denx.de, priyanka.jain@nxp.com,
michael@walle.cc, kernel@puri.sm
Subject: Re: [PATCH v3 0/2] usb: dwc3: add a SPL_USB_DWC3_GENERIC option for the dwc3 driver
Date: Thu, 14 Jul 2022 07:59:34 -0700 [thread overview]
Message-ID: <7e41619ad43e033b74a3dab7ae50e4d7@akkea.ca> (raw)
In-Reply-To: <8e6418ea-9cc3-c79c-a020-bbb56b6ec0a6@denx.de>
On 2022-07-14 07:54, Marek Vasut wrote:
> On 7/14/22 16:52, Angus Ainslie wrote:
>> On 2022-07-14 07:31, Marek Vasut wrote:
>>> On 7/14/22 16:21, Angus Ainslie wrote:
>>>> Hi,
>>>
>>> Hi,
>>>
>>>> Are there any problems with these patches ?
>>>
>>> I missed them, sigh ... sorry.
>>>
>>> Can you rebase them on usb/master and resend, so I can pick them up?
>>
>> Sure, could you remind me how to run the CI tests again.
>
> I don't think you can do that yourself unless you have a repo at
> source.denx.de/u-boot , but I might be wrong.
>
Ah I found it in the gitlab ci script
./tools/buildman/buildman -o /tmp -P -E -W arm
> Really just run git rebase -i on git://source.denx.de/u-boot-usb.git /
> master and then git send-email --annontate , that's all.
Ok I'll send ASAP
next prev parent reply other threads:[~2022-07-14 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 17:15 [PATCH v3 0/2] usb: dwc3: add a SPL_USB_DWC3_GENERIC option for the dwc3 driver Angus Ainslie
2022-05-30 17:15 ` [PATCH v3 1/2] " Angus Ainslie
2022-05-30 17:15 ` [PATCH v3 2/2] configs: get rid of build warnings due to SPL_USB_DWC3_GENERIC Angus Ainslie
2022-06-14 13:30 ` [PATCH v3 0/2] usb: dwc3: add a SPL_USB_DWC3_GENERIC option for the dwc3 driver Angus Ainslie
2022-07-14 14:21 ` Angus Ainslie
2022-07-14 14:31 ` Marek Vasut
2022-07-14 14:52 ` Angus Ainslie
2022-07-14 14:54 ` Marek Vasut
2022-07-14 14:59 ` Angus Ainslie [this message]
2022-07-14 15:04 ` Marek Vasut
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=7e41619ad43e033b74a3dab7ae50e4d7@akkea.ca \
--to=angus@akkea.ca \
--cc=kernel@puri.sm \
--cc=marex@denx.de \
--cc=michael@walle.cc \
--cc=priyanka.jain@nxp.com \
--cc=sbabic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox