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 1001450] Kinetis HAL and driver upgrade Date: Tue, 14 Feb 2012 21:24:00 -0000 [thread overview] Message-ID: <20120214212402.B84982F78008@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001450-777@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=1001450 --- Comment #39 from Christophe Coutand <ecos@hotmail.co.uk> 2012-02-14 21:23:59 GMT --- Hi Ilija, Ok, I was thinking to define CYGNUM_DEVS_FLASH_SPI_SST25XX_DEV0_MAP_ADDR in the devs/flash/plf/ package but you have defined it in the hal/plf/ package. Both methods are fine with me. I will update Bug 1001291 accordingly. Christophe -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2012-02-14 21:24 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-09 18:38 [Bug 1001450] New: Kinetis HAL and driver update bugzilla-daemon 2012-01-09 18:40 ` [Bug 1001450] " bugzilla-daemon 2012-01-09 18:41 ` bugzilla-daemon 2012-01-09 18:43 ` bugzilla-daemon 2012-01-09 18:44 ` bugzilla-daemon 2012-01-09 18:45 ` bugzilla-daemon 2012-01-09 18:47 ` bugzilla-daemon 2012-01-09 18:49 ` bugzilla-daemon 2012-01-09 18:50 ` bugzilla-daemon 2012-01-09 18:53 ` bugzilla-daemon 2012-01-09 19:05 ` bugzilla-daemon 2012-01-09 19:07 ` bugzilla-daemon 2012-01-09 19:08 ` bugzilla-daemon 2012-01-09 19:09 ` bugzilla-daemon 2012-01-09 20:25 ` bugzilla-daemon 2012-01-10 9:03 ` [Bug 1001450] Kinetis HAL and driver upgrade bugzilla-daemon 2012-02-07 19:34 ` bugzilla-daemon 2012-02-07 19:36 ` bugzilla-daemon 2012-02-07 19:38 ` bugzilla-daemon 2012-02-07 19:39 ` bugzilla-daemon 2012-02-07 19:42 ` bugzilla-daemon 2012-02-07 19:43 ` bugzilla-daemon 2012-02-07 19:45 ` bugzilla-daemon 2012-02-07 19:46 ` bugzilla-daemon 2012-02-07 19:47 ` bugzilla-daemon 2012-02-07 19:49 ` bugzilla-daemon 2012-02-07 19:50 ` bugzilla-daemon 2012-02-07 20:07 ` bugzilla-daemon 2012-02-07 20:17 ` bugzilla-daemon 2012-02-07 20:17 ` bugzilla-daemon 2012-02-07 20:44 ` bugzilla-daemon 2012-02-10 21:42 ` bugzilla-daemon 2012-02-12 14:24 ` bugzilla-daemon 2012-02-12 17:35 ` bugzilla-daemon 2012-02-12 19:11 ` bugzilla-daemon 2012-02-12 19:15 ` bugzilla-daemon 2012-02-13 9:41 ` bugzilla-daemon 2012-02-13 14:32 ` bugzilla-daemon 2012-02-13 15:00 ` bugzilla-daemon 2012-02-13 18:21 ` bugzilla-daemon 2012-02-13 18:22 ` bugzilla-daemon 2012-02-14 8:13 ` bugzilla-daemon 2012-02-14 21:24 ` bugzilla-daemon [this message] 2012-02-22 9:06 ` bugzilla-daemon 2012-02-22 9:09 ` bugzilla-daemon 2012-02-22 20:06 ` bugzilla-daemon 2012-02-22 22:45 ` bugzilla-daemon 2012-02-24 7:54 ` bugzilla-daemon 2012-02-24 18:24 ` bugzilla-daemon 2012-02-24 18:49 ` bugzilla-daemon 2012-02-24 19:28 ` bugzilla-daemon 2012-02-24 20:06 ` bugzilla-daemon 2012-05-04 18:15 ` bugzilla-daemon 2012-05-04 18:17 ` bugzilla-daemon 2012-05-04 18:22 ` 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=20120214212402.B84982F78008@mail.ecoscentric.com \ --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).