From: Angelo Dureghello <angelo@sysam.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/7] m68k: remove arch/m68k/lib/board.c
Date: Tue, 17 Mar 2015 07:55:57 +0100 [thread overview]
Message-ID: <5507CFFD.7060405@sysam.it> (raw)
In-Reply-To: <1426563315-31414-4-git-send-email-yamada.masahiro@socionext.com>
On 17/03/2015 04:35, Masahiro Yamada wrote:
> All the M68000 boards have switched to Generic Board.
> This file is no longer necessary.
>
Hi Masahiro,
thanks.
Afaik, me and Alison converted and tested actually only 2 boards
(adding #define CONFIG_SYS_GENERIC_BOARD inside /include/configs/...)
Is this a problem ? Afaik, the user going to build the board
will get a warning that he needs to switch to generic board.
So the same user will be the tester that all works. Correct ?
Best regards,
Angelo
next prev parent reply other threads:[~2015-03-17 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 3:35 [U-Boot] [PATCH v2 0/7] Some improvements related to build system Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 1/7] generic-board: move __HAVE_ARCH_GENERIC_BOARD to Kconfig Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 2/7] generic-board: select SYS_GENERIC_BOARD for some architectures Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 3/7] m68k: remove arch/m68k/lib/board.c Masahiro Yamada
2015-03-17 6:55 ` Angelo Dureghello [this message]
2015-03-25 3:20 ` Masahiro Yamada
2015-03-25 12:12 ` Angelo Dureghello
2015-04-08 19:20 ` Angelo Dureghello
2015-04-09 10:07 ` Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 4/7] malloc_f: remove redundant defalut values of CONFIG_SYS_MALLOC_F_LEN Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 5/7] malloc_f: enable SYS_MALLOC_F by default if DM is on Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 6/7] ARM: bcm283x: merge BCM2835/BCM2836 directories into mach-bcm283x Masahiro Yamada
2015-03-17 3:35 ` [U-Boot] [PATCH v2 7/7] ARM: bcm283x: move SoC headers to mach-bcm283x/include/mach Masahiro Yamada
2015-03-19 10:36 ` Masahiro Yamada
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=5507CFFD.7060405@sysam.it \
--to=angelo@sysam.it \
--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.