From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bmips: fix config warnings from 2019.01
Date: Wed, 2 Jan 2019 23:11:09 +0100 [thread overview]
Message-ID: <5271e352-e923-e44c-767d-796a86a2c37b@gmail.com> (raw)
In-Reply-To: <9150a85d-72a2-58df-d3a9-9c5d59147ac6@denx.de>
Hi Marek,
Check commits 841d5fbae4e993476fa87d8933db0cd58d3c2d41 and
109d8bf3ac7b9bb04f3c46bb540eb2bb865f3dd7.
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=841d5fbae4e993476fa87d8933db0cd58d3c2d41
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=109d8bf3ac7b9bb04f3c46bb540eb2bb865f3dd7
El 01/01/2019 a las 21:24, Marek Vasut escribió:
> On 1/1/19 7:45 PM, Álvaro Fernández Rojas wrote:
>> - Fixes CONFIG_OF_EMBED warning.
>> - Fixes missing CONFIG_BLK warning for CONFIG_USB.
> More details on those warnings that are supposedly fixed would be
> appreciated. It's really unclear what this patch does.
>
next prev parent reply other threads:[~2019-01-02 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 18:45 [U-Boot] [PATCH] bmips: fix config warnings from 2019.01 Álvaro Fernández Rojas
2019-01-01 19:19 ` Tom Rini
2019-01-02 22:09 ` Álvaro Fernández Rojas
2019-01-01 20:24 ` Marek Vasut
2019-01-02 22:11 ` Álvaro Fernández Rojas [this message]
2019-01-02 22:14 ` Tom Rini
2019-01-03 15:51 ` Daniel Schwierzeck
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=5271e352-e923-e44c-767d-796a86a2c37b@gmail.com \
--to=noltari@gmail.com \
--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