From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001184] Cortex-m arch: hal_intr.h includes var_intr.h too early.
Date: Mon, 04 Apr 2011 20:56:00 -0000 [thread overview]
Message-ID: <20110404205623.93D452F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001184-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=1001184
--- Comment #10 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-04-04 21:56:22 BST ---
(In reply to comment #9)
[snip]
> Maybe I tried to be too descriptive. If we opt for short record I think the
> main point is placing #include var_intr.h at right place so I would restate:
>
> * include/hal_intr.h: Remove double inclusion of var_intr.h header and
> include it at proper place.
This CL entry looks great for me. Can you re-post the patch, please?
--
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-04-04 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1001184-104@http.bugs.ecos.sourceware.org/>
2011-04-03 9:13 ` bugzilla-daemon
2011-04-03 21:03 ` bugzilla-daemon
2011-04-03 22:37 ` bugzilla-daemon
2011-04-04 5:54 ` bugzilla-daemon
2011-04-04 10:10 ` bugzilla-daemon
2011-04-04 10:24 ` bugzilla-daemon
2011-04-04 12:25 ` bugzilla-daemon
2011-04-04 13:29 ` bugzilla-daemon
2011-04-04 20:50 ` bugzilla-daemon
2011-04-04 20:56 ` bugzilla-daemon [this message]
2011-04-04 21:27 ` bugzilla-daemon
2011-04-04 21:28 ` bugzilla-daemon
2011-04-05 16:18 ` bugzilla-daemon
2011-04-05 16:48 ` bugzilla-daemon
2011-04-05 17: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=20110404205623.93D452F78001@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).