From: Joerg Wunsch <j@uriah.heep.sax.de>
To: "Weddington, Eric" <Eric.Weddington@atmel.com>
Cc: binutils@sourceware.org, Anatoly Sokolov <aesok@post.ru>,
Denis Chertykov <chertykov@gmail.com>
Subject: Re: [AVR] Add new memory regions to script template
Date: Fri, 18 Mar 2011 09:36:00 -0000 [thread overview]
Message-ID: <20110318093617.GK31558@uriah.heep.sax.de> (raw)
In-Reply-To: <8D64F155F1C88743BFDC71288E8E2DA8E73DFC@csomb01.corp.atmel.com>
As Weddington, Eric wrote:
> Should I just go ahead and commit this, then?
No objections from my side. The offsets used match those that
have been in use in AVaRICE for about a decade now.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
next prev parent reply other threads:[~2011-03-18 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 2:21 Weddington, Eric
2011-03-18 9:36 ` Joerg Wunsch [this message]
2011-03-18 18:33 ` Denis Chertykov
-- strict thread matches above, loose matches on Subject: below --
2011-03-14 14:48 Weddington, Eric
2011-03-30 15:31 ` Nick Clifton
2011-03-31 2:54 ` Weddington, Eric
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=20110318093617.GK31558@uriah.heep.sax.de \
--to=j@uriah.heep.sax.de \
--cc=Eric.Weddington@atmel.com \
--cc=aesok@post.ru \
--cc=binutils@sourceware.org \
--cc=chertykov@gmail.com \
--cc=joerg_wunsch@uriah.heep.sax.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).