public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "H Hartley Sweeten" <hartleys@visionengravers.com>
To: "Gary Thomas" <gary@mlbassoc.com>, 	"Jonathan Larmour" <jifl@jifvik.org>
Cc: <ecos-patches@ecos.sourceware.org>,
		"eCos Maintainers" <ecos-maintainers@ecos.sourceware.org>
Subject: RE: Cirrus Logic EP93XX ARM9 support
Date: Wed, 16 Sep 2009 21:31:00 -0000	[thread overview]
Message-ID: <BD79186B4FD85F4B8E60E381CAEE190901CBF43E@mi8nycmail19.Mi8.com> (raw)
In-Reply-To: <4A35A196.9010801@mlbassoc.com>

On Sunday, June 14, 2009 6:19 PM, Gary Thomas wrote:
> Jonathan Larmour wrote:
>> Gary Thomas wrote:
>>> H Hartley Sweeten wrote:
>>>
>>>> Hello all,
>>>>
>>>> Does anyone know the status of the Cirrus Logic EP93XX ARM9 support?
>>>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739
>>>>
>>>> Was the copyright assignment to the FSF completed?  If so, would it
>>>> be possible to at least get the new file pieces of the patch into
>>>> CVS so that they can be cleaned up?  The diff appears fairly clean
>>>> except for a couple of issues.  Following are the files in the patch.
>>>>
>>>
>>>
>>> AFAIK, we've not had official confirmation from FSF yet.
>> 
>> Unless they've submitted it very recently, then I suspect they never
>> made an assignment.
>
> They claim to have submitted it [not so] recently - probably April
> timeframe, maybe a bit later.  It should be in the logs (I don't have
> time to search right now).

Does anyone know the status of this?

I have a number of updates/cleanups I would like to submit but the
original patch is still not in CVS.

Thanks for your time,
Hartley

  reply	other threads:[~2009-09-16 21:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BD79186B4FD85F4B8E60E381CAEE1909019173AD@mi8nycmail19.Mi8.com>
2009-06-10 19:42 ` Gary Thomas
2009-06-14 21:02   ` Jonathan Larmour
2009-06-15  1:19     ` Gary Thomas
2009-09-16 21:31       ` H Hartley Sweeten [this message]
2009-09-17  8:54         ` John Dallaway
2009-09-17 20:54         ` Jonathan Larmour
2009-09-17 21:10           ` H Hartley Sweeten
2009-09-17 21:18             ` Austin, Brian
2009-11-18 16:31               ` H Hartley Sweeten
2009-11-18 16:33                 ` Austin, Brian
2009-11-19  9:37                   ` John Dallaway
2009-11-19 18:38                   ` Jonathan Larmour
2010-03-13  0:08                     ` H Hartley Sweeten
2009-08-07 15:36   ` John Dallaway
2009-08-07 15:53     ` Austin, Brian
2009-08-07 16:19       ` John Dallaway

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=BD79186B4FD85F4B8E60E381CAEE190901CBF43E@mi8nycmail19.Mi8.com \
    --to=hartleys@visionengravers.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    --cc=jifl@jifvik.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).