From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/8 V2 Part 1/3] add at91 SoC access with c structures
Date: Sat, 16 Jan 2010 21:35:34 +0100 [thread overview]
Message-ID: <hit7n0$b7k$1@ger.gmane.org> (raw)
In-Reply-To: <4B52219B.1040900@scharsoft.de>
Sorry should named
[PATCH 5/8 V2 Part 2/3] add at91 SoC access with c structures
next prev parent reply other threads:[~2010-01-16 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 20:29 [U-Boot] [PATCH 5/8 V2 Part 1/3] add at91 SoC access with c structures Jens Scharsig
2010-01-16 20:35 ` Jens Scharsig [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-16 20:29 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='hit7n0$b7k$1@ger.gmane.org' \
--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.