How to handle patches for it AM33?

How to handle patches for it AM33?

[Andreas Jaeger]

I have posted a patch for AM33 and nobody reviewed it - it seems we do 
not have a maintainer.

Will someobdy else step up and review this, should I ignore am33 - or 
just commit it?

Andreas
-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

Re: How to handle patches for it AM33?

[Joseph S. Myers]

On Sun, 10 Mar 2013, Andreas Jaeger wrote:

> I have posted a patch for AM33 and nobody reviewed it - it seems we do not
> have a maintainer.
> 
> Will someobdy else step up and review this, should I ignore am33 - or just
> commit it?

My view is just commit if you have a patch.  We've been waiting since I 
reviewed the update patch 
<http://sourceware.org/ml/libc-ports/2012-06/msg00066.html> for a revised 
version that takes account of my review (and of course of all the global 
changes in libc since then that require corresponding port changes).

-- 
Joseph S. Myers
joseph@codesourcery.com