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 1001463] LPC17XX supplementary code/option patch
Date: Thu, 26 Jan 2012 09:05:00 -0000	[thread overview]
Message-ID: <20120126090503.BD7EC2F78001@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001463-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=1001463

--- Comment #3 from Bernard Fouché <bernard.fouche@kuantic.com> 2012-01-26 09:05:01 GMT ---
(In reply to comment #2)
> Hi Bernard
> 
> Thank you for your contribution.
> 
> Past couple of days I have committed patches for Bug 1001395 (including bug
> 1001443) and Bug 1001432. You may need to synchronize your patches accordingly.

I've first updated my copy of ecos-cvs before making the patch. More exactly I
was waiting for you to commit to make my patch ;-)

> 
> I could see that some patches cover issues reported (by you) in other bugs. Can
> you submit them there (and obsolete some patches of my own of course)?
> Splitting patches will speed up check in for some of them.

You are probably referring to bug #1001407. Yes the proposed patch includes
changes similar to attachment 1481 (however I didn't use the word 'omplemented'
in the comments ;-)) but it adds many more hardware related definitions. Maybe
you commit your patch, and then I'll submit a new one that won't have the same
fixes? At the moment I have chosen to make my diff vs the ecos cvs repo and I
don't consider pending patches. Maybe I should do differently?

> 
> Also, on your initiative we have started some discussion on bit banding at Bug
> 1001442 so we can continue there with your patches.

So let's first decide how bitband is handled and afterwards I'll update the
proposed patch accordingly. Or I can remove the bitband macros in the proposed
patch.

-- 
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.

  parent reply	other threads:[~2012-01-26  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 16:17 [Bug 1001463] New: " bugzilla-daemon
2012-01-25 16:18 ` [Bug 1001463] " bugzilla-daemon
2012-01-25 21:42 ` bugzilla-daemon
2012-01-26  9:05 ` bugzilla-daemon [this message]
2012-01-26 10:18 ` 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=20120126090503.BD7EC2F78001@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).