All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM status or maintainer info currently missing
Date: Thu, 2 Jul 2015 09:48:31 +0530	[thread overview]
Message-ID: <5594BB97.6050308@ti.com> (raw)
In-Reply-To: <20150701151340.5ac6044a@lilith>

Hi Albert,
On Wednesday 01 July 2015 06:43 PM, 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' 
Posted a patch for both am43xx_evm* boards.
http://patchwork.ozlabs.org/patch/490416/

Thanks and regards,
Lokesh

  parent reply	other threads:[~2015-07-02  4:18 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
2015-07-02  4:18 ` Lokesh Vutla [this message]
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=5594BB97.6050308@ti.com \
    --to=lokeshvutla@ti.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.