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 1001752] fixed endianness issues with Freescale eDMA and DSPI driver to also support PowerPC MPC5xxx in addition to Kinetis
Date: Wed, 06 Feb 2013 17:25:00 -0000	[thread overview]
Message-ID: <bug-1001752-104-WrjExvZL0u@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001752-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=1001752

--- Comment #8 from Ilija Kocho <ilijak@siva.com.mk> ---
Hi Stefan

I take it STS stands for Stefan Singer. However it would be better to put
complete name in ChangeLog. Your e-mail address would indicate that this is
Freescale contribution which is important because we have Freescale's copyright
assignment.

Also the attachment for "DSPI ChaneLog" seem to contain wrong file :).

If it doesn't make harder for you, it would make easier for me if you post
integral patches against current CVS.

I can take care about formatting.

Ilija

(In reply to comment #7)
> Hi Ilija,
> I have tested your additions and they seem to work on MPC5668G. I have
> updated the changelog for the two modules and took the liberty to add both
> of us as authors for that. Regarding the cleanup of formating I guess I must
> have some strange setting in Eclipse, since it looks fine on my end, but I
> have heard before, that files from my side might have some issues here.
> Unfortunately I do not know, how to correct this.
> 
> Thanks
> Stefan

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

  parent reply	other threads:[~2013-02-06 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 16:08 [Bug 1001752] New: " bugzilla-daemon
2013-02-04 16:09 ` [Bug 1001752] " bugzilla-daemon
2013-02-04 16:10 ` bugzilla-daemon
2013-02-04 16:47 ` bugzilla-daemon
2013-02-05 13:22 ` bugzilla-daemon
2013-02-05 13:29 ` bugzilla-daemon
2013-02-06 16:51 ` bugzilla-daemon
2013-02-06 16:53 ` bugzilla-daemon
2013-02-06 16:55 ` bugzilla-daemon
2013-02-06 17:25 ` bugzilla-daemon [this message]
2013-02-11 16:43 ` bugzilla-daemon
2013-02-11 16:45 ` bugzilla-daemon
2013-02-11 16:46 ` bugzilla-daemon
2013-02-12 21:03 ` bugzilla-daemon
2013-02-12 21:05 ` bugzilla-daemon
2013-02-13 10:18 ` bugzilla-daemon
2013-02-13 10:23 ` bugzilla-daemon
2013-02-24 11:22 ` bugzilla-daemon
2017-02-15  7:19 ` 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-1001752-104-WrjExvZL0u@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).