From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch 0/8] add at91 SoC access with c structures
Date: Tue, 22 Dec 2009 08:39:33 +0100 [thread overview]
Message-ID: <4B3077B5.8010108@scharsoft.de> (raw)
In-Reply-To: <4B2FF24A.9020201@windriver.com>
Hello Tom,
>>
>> I hope there are somewhere a some volunteers to make the next steps.
>>
> Jens,
> Will you be able to make the revisions to this patchset ?
> Tom
>
Yes, I will. But I have not time enough to convert other boards
and drivers.
Best regards
Jens Scharsig
prev parent reply other threads:[~2009-12-22 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 20:08 [U-Boot] [Patch 0/8] add at91 SoC access with c structures Jens Scharsig
[not found] ` <4B2FF24A.9020201@windriver.com>
2009-12-22 7:39 ` 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=4B3077B5.8010108@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