From: Tom Rini <trini@konsulko.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>, u-boot@lists.denx.de
Subject: Re: [PATCH] bmips: Add Inteno XG6846 board
Date: Mon, 25 Sep 2023 10:22:03 -0400 [thread overview]
Message-ID: <20230925142203.GX305624@bill-the-cat> (raw)
In-Reply-To: <CACRpkdYWK15i=KEFc_VM+xqgmmnT6AQX3OgnznFrmPhkjCfOiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Mon, Sep 25, 2023 at 03:56:07PM +0200, Linus Walleij wrote:
> On Thu, Sep 21, 2023 at 7:25 PM Tom Rini <trini@konsulko.com> wrote:
> > On Thu, Sep 21, 2023 at 04:00:24PM +0200, Daniel Schwierzeck wrote:
> >
> > [snip]
> > > I just tested it, you can simply add an empty board/inteno/xg6846/Makefile and
> > > remove board/inteno/xg6846/xg6846.c. But you can also remove the Makefile.
> > > Just the Kconfig and MAINTAINERS file are needed.
> >
> > An empty Makefile is OK, but no Makefile requires a bit more as we first
> > try and include it unconditionally and then try and link in built-in.o.
> > I'm poking at this now.
>
> Did you get anywhere with this? If it's on the master I'll just rebase and
> be done with it, else I can go with an empty Makefile simply.
Please rebase on top of:
https://patchwork.ozlabs.org/project/uboot/list/?series=374302
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-09-25 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 7:42 [PATCH] bmips: Add Inteno XG6846 board Linus Walleij
2023-09-20 14:22 ` Tom Rini
2023-09-20 18:51 ` Linus Walleij
2023-09-20 18:55 ` Tom Rini
2023-09-21 14:00 ` Daniel Schwierzeck
2023-09-21 15:53 ` Tom Rini
2023-09-21 17:25 ` Tom Rini
2023-09-25 13:56 ` Linus Walleij
2023-09-25 14:22 ` Tom Rini [this message]
2023-09-21 14:03 ` Daniel Schwierzeck
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=20230925142203.GX305624@bill-the-cat \
--to=trini@konsulko.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=linus.walleij@linaro.org \
--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.