From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/3] Only attempt to build USB driver model in SPL when required
Date: Mon, 26 Nov 2018 11:22:18 +0100 [thread overview]
Message-ID: <7c8f94b9-99cf-8408-4ef0-a027f72ebf50@denx.de> (raw)
In-Reply-To: <e5bcb4d084cad27ee5f5697564fa6754396a1139.camel@collabora.com>
On 11/26/2018 11:20 AM, Martyn Welch wrote:
> On Sat, 2018-11-24 at 19:25 +0100, Marek Vasut wrote:
>> On 11/23/2018 05:47 PM, Martyn Welch wrote:
>>> Current define usage causes tooling to attempt to build for USB
>>> driver
>>> model when building non-DM SPL. Update logic to avoid this.
>>>
>>> Signed-off-by: Martyn Welch <martyn.welch@collabora.com>
>>>
>>> ---
>>
>> Isn't this exact problem fixed in u-boot-usb/master ?
>>
>
> Any changes I've missed in master didn't clash with this when I rebase
> to master. I also get build errors when attempting to build from master
> with this patch removed.
By master you mean u-boot/master or u-boot-usb/master ?
Trimming CC and CCing Simon.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-11-26 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 16:47 [U-Boot] [PATCH v2 1/3] Enable FEC driver to retrieve PHY address from device tree Martyn Welch
2018-11-23 16:47 ` [U-Boot] [PATCH v2 2/3] Only attempt to build USB driver model in SPL when required Martyn Welch
2018-11-24 18:25 ` Marek Vasut
2018-11-26 10:20 ` Martyn Welch
2018-11-26 10:22 ` Marek Vasut [this message]
2018-11-26 15:23 ` Simon Goldschmidt
2018-11-26 15:27 ` Marek Vasut
2018-11-26 16:16 ` Martyn Welch
2018-11-26 18:21 ` Marek Vasut
2018-11-23 16:47 ` [U-Boot] [PATCH v2 3/3] imx: Add PHYTEC phyBOARD-i.MX6UL-Segin Martyn Welch
2018-11-27 14:15 ` Wadim Egorov
2018-12-03 16:34 ` Martyn Welch
2018-11-27 17:34 ` Marek Vasut
2018-12-03 16:35 ` Martyn Welch
2018-11-24 12:25 ` [U-Boot] [PATCH v2 1/3] Enable FEC driver to retrieve PHY address from device tree Lukasz Majewski
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=7c8f94b9-99cf-8408-4ef0-a027f72ebf50@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox