public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001649] AT91 hal extension Date: Sun, 10 Mar 2013 16:56:00 -0000 [thread overview] Message-ID: <bug-1001649-777-BNcZ0ydBdi@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1001649-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001649 Ilija Kocho <ilijak@siva.com.mk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ilijak@siva.com.mk --- Comment #13 from Ilija Kocho <ilijak@siva.com.mk> --- Bernd The attachment 1934 seem to have pretty much ARM9 architecure patches. Could architecture stuff be isolated in a separate bug? If we could integrate the AT91 support independently of architecture it would be much simpler, cleaner and safer process. Ilija -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2013-03-10 16:56 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-10 16:30 [Bug 1001649] New: " bugzilla-daemon 2012-08-10 16:31 ` [Bug 1001649] " bugzilla-daemon 2012-08-10 16:33 ` bugzilla-daemon 2012-08-10 16:34 ` bugzilla-daemon 2012-08-10 16:38 ` bugzilla-daemon 2012-08-10 16:40 ` bugzilla-daemon 2012-08-10 16:43 ` bugzilla-daemon 2012-08-14 7:45 ` bugzilla-daemon 2012-08-20 7:41 ` bugzilla-daemon 2012-08-20 7:51 ` bugzilla-daemon 2012-08-20 8:13 ` bugzilla-daemon 2012-09-13 11:09 ` bugzilla-daemon 2012-09-13 11:15 ` bugzilla-daemon 2012-09-13 11:16 ` bugzilla-daemon 2012-09-13 11:28 ` bugzilla-daemon 2013-03-10 16:56 ` bugzilla-daemon [this message] 2013-03-10 17:10 ` bugzilla-daemon 2013-03-11 14:05 ` bugzilla-daemon 2013-03-11 15:19 ` bugzilla-daemon 2013-03-15 1:29 ` 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=bug-1001649-777-BNcZ0ydBdi@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.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: linkBe 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).