From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM status or maintainer info currently missing
Date: Wed, 1 Jul 2015 13:37:28 +0000 [thread overview]
Message-ID: <1435757848.4689.47.camel@synopsys.com> (raw)
In-Reply-To: <20150701151340.5ac6044a@lilith>
Hi Albert,
On Wed, 2015-07-01 at 15:13 +0200, Albert ARIBAUD wrote:
> Hello all,
>
> I get the following when building current u-boot-arm/master with
> current u-boot/master:
>
> * WARNING: no status info for 'am43xx_evm_ethboot'
> * WARNING: no maintainers for 'am43xx_evm_ethboot'
> WARNING: no status info for 'cairo'
> WARNING: no maintainers for 'cairo'
> WARNING: no status info for 'axs103'
> WARNING: no maintainers for 'axs103'
> WARNING: no status info for 'socfpga_arria5'
> WARNING: no maintainers for 'socfpga_arria5'
> WARNING: no status info for 'at91sam9rlek_mmc'
> WARNING: no maintainers for 'at91sam9rlek_mmc'
> WARNING: no status info for 'odroid-xu3'
> WARNING: no maintainers for 'odroid-xu3'
> * WARNING: no status info for 'am335x_baltos'
> * WARNING: no maintainers for 'am335x_baltos'
> * WARNING: no status info for 'am43xx_evm_usbhost_boot'
> * WARNING: no maintainers for 'am43xx_evm_usbhost_boot'
> WARNING: no status info for 'at91sam9g20ek_2mmc'
> WARNING: no maintainers for 'at91sam9g20ek_2mmc'
> WARNING: no status info for 'db-88f6820-gp'
> WARNING: no maintainers for 'db-88f6820-gp'
>
> "*" means warning is new in mainline.
>
> In most cases, the board's MAINTAINERS file also lacks an 'F:' entry
> for
> the board's defconfig -- or the board is lacking a MAINTAINERS file
> entirely.
I'l add an entry for axs103.
-Alexey
next prev parent reply other threads:[~2015-07-01 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 13:13 [U-Boot] ARM status or maintainer info currently missing Albert ARIBAUD
2015-07-01 13:31 ` Pavel Machek
2015-07-01 16:52 ` Marek Vasut
2015-07-01 13:35 ` Yegor Yefremov
2015-07-01 13:37 ` Alexey Brodkin [this message]
2015-07-02 4:18 ` Lokesh Vutla
2015-07-05 17:34 ` Albert ARIBAUD
2015-07-05 18:35 ` Yegor Yefremov
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=1435757848.4689.47.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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 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.