From: Sam Ravnborg <sam@ravnborg.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/9] ARM: misc cleanups
Date: Tue, 28 Feb 2023 18:37:08 +0100 [thread overview]
Message-ID: <Y/47xKrQwNGDe2KU@ravnborg.org> (raw)
In-Reply-To: <20230228143031.1718565-1-s.hauer@pengutronix.de>
Hi Sascha,
On Tue, Feb 28, 2023 at 03:30:22PM +0100, Sascha Hauer wrote:
> I am working on making it possible to build support for multiple
> arch/arm/mach-*/ into the same barebox. Here are some misc cleanups
> I stumbled upon while preparing multi arch support.
>
> Sascha Hauer (9):
> ARM: mxs: remove unused mach/clock.h
> ARM: imx: remove unused mach/clock.h
> ARM: rockchip: drop mach/timer.h
> ARM: i.MX: Move imxfb.h to include/platform_data/
> pinctrl: rockchip: Fix uninitialized var warning
> ARM: at91: remove unnecessary configs
> ARM: at91: Switch all boards to multiimage
> at91: consolidate usb-a963 128m images
> ARM: pxa: Move plat/ include files to mach/
As much as I like the patches I think a more sane course of
action for these old at91 boards would be to drop most of them.
A simple algorithm would be:
If not supported in the kernel, drop the board.
The boards that are not in the kernel have not seen any
activity in barebox for a long time, so it is not like
they look maintained.
That would allow us to get rid of some legacy stuff in
mach-at91 and maybe motivate someone like me to actually
work on the remaining boards as it then looks
doable to convert the remaining boards to DT.
Sam
next prev parent reply other threads:[~2023-02-28 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 14:30 Sascha Hauer
2023-02-28 14:30 ` [PATCH 1/9] ARM: mxs: remove unused mach/clock.h Sascha Hauer
2023-02-28 14:30 ` [PATCH 2/9] ARM: imx: " Sascha Hauer
2023-02-28 14:30 ` [PATCH 3/9] ARM: rockchip: drop mach/timer.h Sascha Hauer
2023-02-28 14:30 ` [PATCH 4/9] ARM: i.MX: Move imxfb.h to include/platform_data/ Sascha Hauer
2023-02-28 14:30 ` [PATCH 5/9] pinctrl: rockchip: Fix uninitialized var warning Sascha Hauer
2023-02-28 14:30 ` [PATCH 6/9] ARM: at91: remove unnecessary configs Sascha Hauer
2023-02-28 14:30 ` [PATCH 7/9] ARM: at91: Switch all boards to multiimage Sascha Hauer
2023-02-28 14:30 ` [PATCH 8/9] at91: consolidate usb-a963 128m images Sascha Hauer
2023-02-28 14:30 ` [PATCH 9/9] ARM: pxa: Move plat/ include files to mach/ Sascha Hauer
2023-03-01 17:42 ` Ahmad Fatoum
2023-02-28 17:37 ` Sam Ravnborg [this message]
2023-03-01 7:53 ` [PATCH 0/9] ARM: misc cleanups Sascha Hauer
2023-03-02 17:01 ` Sam Ravnborg
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=Y/47xKrQwNGDe2KU@ravnborg.org \
--to=sam@ravnborg.org \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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