From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/8 V2] add at91 SoC access with c structures
Date: Sun, 17 Jan 2010 18:48:31 +0100 [thread overview]
Message-ID: <4B534D6F.1000704@scharsoft.de> (raw)
In-Reply-To: <4B534492.5010203@windriver.com>
Hello Tom
> It is unclear why arm920t/at91rm9200 -> arm920t/at91
> I am not in favor of renaming dirs or making multiple copies
> of the same file.
the intention is, the at91rm9200 integrates in at91 tree.
So I create a new dir for files with c structur soc access.
If all boards converted to at91 new soc access, we can remove the
at91rm9200 dir.
see also <http://lists.denx.de/pipermail/u-boot/2009-December/065688.html>
regards Jens
prev parent reply other threads:[~2010-01-17 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 20:28 [U-Boot] [PATCH 2/8 V2] add at91 SoC access with c structures Jens Scharsig
2010-01-17 17:10 ` Tom
2010-01-17 17:48 ` Jens Scharsig [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=4B534D6F.1000704@scharsoft.de \
--to=js_at_ng@scharsoft.de \
--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.