public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001837] Rich FlexBus RAM layout
Date: Sat, 18 May 2013 19:14:00 -0000	[thread overview]
Message-ID: <bug-1001837-104-aAYUHp2tVr@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001837-104@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=1001837

--- Comment #18 from Ilija Kocho <ilijak@siva.com.mk> ---
Created attachment 2236
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2236&action=edit
TWR-K60N512-FXM rich FlexBus RAM add on 130518 incremental to 2223

This patch adds requirement for FXM memory for TWR-K60N512-FXM when necessary.
Incremental to Attachment 2223.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2013-05-18 19:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 13:22 [Bug 1001837] New: " bugzilla-daemon
2013-04-30 13:24 ` [Bug 1001837] " bugzilla-daemon
2013-04-30 13:25 ` bugzilla-daemon
2013-05-02  8:44 ` bugzilla-daemon
2013-05-02  8:45 ` bugzilla-daemon
2013-05-03  5:40 ` bugzilla-daemon
2013-05-03  9:05 ` bugzilla-daemon
2013-05-03 16:51 ` bugzilla-daemon
2013-05-03 16:52 ` bugzilla-daemon
2013-05-03 16:52 ` bugzilla-daemon
2013-05-03 16:53 ` bugzilla-daemon
2013-05-03 17:10 ` bugzilla-daemon
2013-05-03 17:24 ` bugzilla-daemon
2013-05-03 17:48 ` bugzilla-daemon
2013-05-03 18:00 ` bugzilla-daemon
2013-05-03 18:01 ` bugzilla-daemon
2013-05-03 18:06 ` bugzilla-daemon
2013-05-04 16:20 ` bugzilla-daemon
2013-05-05 16:16 ` bugzilla-daemon
2013-05-18 19:14 ` bugzilla-daemon [this message]
2013-06-01 22:46 ` bugzilla-daemon
2013-06-01 22:50 ` bugzilla-daemon
2013-06-01 22:54 ` bugzilla-daemon
2013-06-02 17:12 ` 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-1001837-104-aAYUHp2tVr@http.bugs.ecos.sourceware.org/ \
    --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).