public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: Fix warning by building vf610twr_nand
Date: Tue, 16 Sep 2014 21:02:04 +0200	[thread overview]
Message-ID: <f923c052e46bc2e515fc8665871b5d18@agner.ch> (raw)
In-Reply-To: <1410876484-10060-1-git-send-email-sbabic@denx.de>

Hi,

Didn't realized that this config needs a maintainer too, sorry. I agree,
since the vf610twr is maintained by Alison, it makes sense that the nand
variant is maintained by Alison too..

Thanks for the patch.

--
Stefan

Am 2014-09-16 16:08, schrieb Stefano Babic:
> commit d6d07a9b... arm: vf610: add NAND support for vf610twr
> generates the following warnings:
> 
> WARNING: no status info for 'vf610twr_nand'
> WARNING: no maintainers for 'vf610twr_nand'WARNING: no status info for
> 'vf610twr_nand'
> 
> This is due to the fact that vf610twr_nand_defconfig has no Maintainer.
> This patch proposed Alison as Maintainer and fix it.
> 
> Signed-off-by: Stefano Babic <sbabic@denx.de>
> CC: Alison Wang <b18965@freescale.com>
> CC: Stefan Agner <stefan@agner.ch>
> ---
>  board/freescale/vf610twr/MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/board/freescale/vf610twr/MAINTAINERS
> b/board/freescale/vf610twr/MAINTAINERS
> index 56a09c9..f2997f0 100644
> --- a/board/freescale/vf610twr/MAINTAINERS
> +++ b/board/freescale/vf610twr/MAINTAINERS
> @@ -4,3 +4,4 @@ S:	Maintained
>  F:	board/freescale/vf610twr/
>  F:	include/configs/vf610twr.h
>  F:	configs/vf610twr_defconfig
> +F:	configs/vf610twr_nand_defconfig

  reply	other threads:[~2014-09-16 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 14:08 [U-Boot] [PATCH] imx: Fix warning by building vf610twr_nand Stefano Babic
2014-09-16 19:02 ` Stefan Agner [this message]
     [not found] ` <b623b032e889481ba9e411d612fd9879@BN1PR0301MB0689.namprd03.prod.outlook.com>
2014-09-17  8:09   ` Stefano Babic

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=f923c052e46bc2e515fc8665871b5d18@agner.ch \
    --to=stefan@agner.ch \
    --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