From: Paul Burton <paul.burton@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Nathan Sullivan <nathan.sullivan@ni.com>, <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-mips@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] MIPS: NI 169445 board support
Date: Mon, 7 Aug 2017 10:24:05 -0700 [thread overview]
Message-ID: <11583742.zienCqJRO5@np-p-burton> (raw)
In-Reply-To: <20170807152648.GA13214@linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
Hi Ralf,
On Monday, 7 August 2017 08:26:48 PDT Ralf Baechle wrote:
> On Tue, Jul 18, 2017 at 01:29:09PM -0500, Nathan Sullivan wrote:
> > diff --git a/arch/mips/generic/vmlinux.its.S
> > b/arch/mips/generic/vmlinux.its.S index f67fbf1..de851f7 100644
> > --- a/arch/mips/generic/vmlinux.its.S
> > +++ b/arch/mips/generic/vmlinux.its.S
> > @@ -29,3 +29,28 @@
> >
> > };
> >
> > };
> >
> > };
> >
> > +
> > +#ifdef CONFIG_FIT_IMAGE_FDT_NI169445
> > +/ {
> > + images {
>
> [...]
>
> > + };
> > +};
> > +#endif
>
> There's been a reject on this file because of a Boston #ifdefed section.
> I've fixed that up but we need a cleaner solution. Paul, any suggestions?
>
> Ralf
One possibility would be for us to split the board portions of vmlinux.its.S
out into a file per-board, perhaps board-boston.its.S, board-ni169445.its.S
etc. The build process would then have to concatenate the right files to
generate the full image tree source.
Does that sound good to you?
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-07 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 18:29 Nathan Sullivan
2017-07-24 16:06 ` Rob Herring
2017-08-07 15:26 ` Ralf Baechle
2017-08-07 15:32 ` Nathan Sullivan
2017-08-07 17:24 ` Paul Burton [this message]
2017-08-07 21:36 ` Ralf Baechle
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=11583742.zienCqJRO5@np-p-burton \
--to=paul.burton@imgtec.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=nathan.sullivan@ni.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®