From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001117] Cortex-M arch. Provision for overriding of VTOR setting.
Date: Mon, 17 Jan 2011 21:32:00 -0000 [thread overview]
Message-ID: <20110117213232.85C9D2F80001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001117-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001117
Sergei Gavrikov <sergei.gavrikov@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sergei.gavrikov@gmail.com
--- Comment #4 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-01-17 21:32:30 GMT ---
Ilija, your argument about protection the VTOR placement is clear. The patch
looks good for me. If nobody have doubts I plan to apply it.
[OFF-TOPIC]
Iljia, I noticed that you stick on the 'defined' operator
http://gcc.gnu.org/onlinedocs/cpp/Defined.html#Defined
It is curious why do not use ifdef/ifndef in proper places?
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-17 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1001117-104@http.bugs.ecos.sourceware.org/>
2011-01-16 8:54 ` [Bug 1001117] Cortex-M architecture fixes bugzilla-daemon
2011-01-16 10:21 ` bugzilla-daemon
2011-01-16 14:06 ` bugzilla-daemon
2011-01-16 14:15 ` bugzilla-daemon
2011-01-17 8:30 ` [Bug 1001117] Cortex-M arch. Provision for overriding of VTOR setting bugzilla-daemon
2011-01-17 21:32 ` bugzilla-daemon [this message]
2011-01-18 2:00 ` bugzilla-daemon
2011-01-19 19:00 ` bugzilla-daemon
2011-01-19 19:02 ` bugzilla-daemon
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=20110117213232.85C9D2F80001@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.org \
/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).