From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] is it worth enhancing cmd_immap.c to handle 83xx?
Date: Thu, 14 Jan 2016 15:47:40 -0500 [thread overview]
Message-ID: <20160114204740.GX3359@bill-the-cat> (raw)
In-Reply-To: <alpine.LFD.2.20.1512220611020.14374@localhost>
On Tue, Dec 22, 2015 at 06:13:45AM -0500, Robert P. J. Day wrote:
> as i'm currently messing with MPC8360e-based board, is there any
> value in submitting a patch so that cmd_immap.c can handle 83xx? it
> seems pretty straightforward. i'm also working on the politics of
> being allowed to submit a patch to deal with an MPC8360e-based system
> currently being ported to linux so that that cmd_immap.c enhancement
> would have actual value.
If you're able to mainline other useful things with MPC83xx yes,
otherwise, probably not.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160114/7eb47e7d/attachment.sig>
prev parent reply other threads:[~2016-01-14 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 11:13 [U-Boot] is it worth enhancing cmd_immap.c to handle 83xx? Robert P. J. Day
2016-01-14 20:47 ` Tom Rini [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=20160114204740.GX3359@bill-the-cat \
--to=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox