From: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
To: Paul Burton <paul.burton-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: Nathan Sullivan <nathan.sullivan-acOepvfBmUk@public.gmane.org>,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v6] MIPS: NI 169445 board support
Date: Mon, 7 Aug 2017 23:36:03 +0200 [thread overview]
Message-ID: <20170807213603.GE3509@linux-mips.org> (raw)
In-Reply-To: <11583742.zienCqJRO5@np-p-burton>
On Mon, Aug 07, 2017 at 10:24:05AM -0700, Paul Burton wrote:
> 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?
Yes, that sounds good.
Ralf
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-07 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 18:29 [PATCH v6] MIPS: NI 169445 board support Nathan Sullivan
[not found] ` <1500402549-12090-1-git-send-email-nathan.sullivan-acOepvfBmUk@public.gmane.org>
2017-07-24 16:06 ` Rob Herring
2017-08-07 15:26 ` Ralf Baechle
2017-08-07 15:32 ` Nathan Sullivan
[not found] ` <20170807152648.GA13214-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
2017-08-07 17:24 ` Paul Burton
2017-08-07 21:36 ` Ralf Baechle [this message]
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=20170807213603.GE3509@linux-mips.org \
--to=ralf-6z/3iimg2c8g8few9mqtra@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=nathan.sullivan-acOepvfBmUk@public.gmane.org \
--cc=paul.burton-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).