From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] is it worth enhancing cmd_immap.c to handle 83xx?
Date: Tue, 22 Dec 2015 06:13:45 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1512220611020.14374@localhost> (raw)
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.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2015-12-22 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 11:13 Robert P. J. Day [this message]
2016-01-14 20:47 ` [U-Boot] is it worth enhancing cmd_immap.c to handle 83xx? Tom Rini
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=alpine.LFD.2.20.1512220611020.14374@localhost \
--to=rpjday@crashcourse.ca \
--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