From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8 V2] add at91 SoC access with c structures
Date: Sun, 17 Jan 2010 18:48:42 +0100 [thread overview]
Message-ID: <4B534D7A.8030804@scharsoft.de> (raw)
In-Reply-To: <4B522170.5060901@scharsoft.de>
Please look at
<http://lists.denx.de/pipermail/u-boot/2009-December/065688.html>
for Patchset details
next prev parent reply other threads:[~2010-01-17 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 20:28 [U-Boot] [PATCH 1/8 V2] add at91 SoC access with c structures Jens Scharsig
2010-01-17 17:34 ` Tom
2010-01-17 17:48 ` Jens Scharsig [this message]
2010-01-17 18:25 ` Tom
2010-01-17 19:02 ` Jens Scharsig
2010-01-23 11:00 ` Jens Scharsig
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=4B534D7A.8030804@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox