Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] uclibc config cleanup
Date: Fri, 01 Jul 2011 00:41:07 +0100	[thread overview]
Message-ID: <1309477267.20015.501.camel@rex> (raw)
In-Reply-To: <BANLkTim6Qvrc1K8788QMHCZArRvZ=MZ0WA@mail.gmail.com>

On Thu, 2011-06-30 at 16:36 -0700, Khem Raj wrote:
> On Thu, Jun 30, 2011 at 3:30 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Thu, 2011-06-30 at 01:06 -0700, Khem Raj wrote:
> >> We do not need machine configs or even arch configs since we construct the bits
> >> in .inc files. Once anamoly is mips where we do not use default ARCH for o32
> >> which is mips1 but we use mips32 so thats the reason we have a separate config
> >> for mips.
> >>
> >> Additionally fix boot issue found on mips which were exposed by udev 171
> >>
> >> These patches have been tested with builds from scratch for all supported qemu machines
> >> and incrmental too (for qemumips)
> >> and angstrom/console-image is booted on all supported qemu machines
> >>
> >> The following changes since commit ae4c2b8834dc4d88be7207ea5c45c596bb46fded:
> >>
> >>   uclibc: Fix bug exposed by udev 168+ for mips architecture (2011-06-30 00:52:32 -0700)
> >>
> >> are available in the git repository at:
> >>   git://git.openembedded.org/openembedded-core-contrib kraj/uclibc-cleanup
> >>   http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/uclibc-cleanup
> >>
> >> Khem Raj (6):
> >>   uclibc: Remove redundant machine/arch configs
> >>   uclibc-config.inc: Fix regexp to determine big-endian arm
> >>   uclibc.inc: Use ARCH_WANTS_{LITTLE|BIG}_ENDIAN to denote endian
> >>   uclibc_git.bb: Untether UCLIBC_HAS_FPU from UCLIBC_HAS_FLOATS
> >>   uclibc: Add UCLIBC_HAS_FLOATS=y to uClibc.distro
> >>   uclibc: Fix bug exposed by udev 168+ for mips architecture
> >
> > Merged to master, thanks.
> 
> Hi Richard
> 
> Somehow first patch that got merged was older version I guess from the
> one I posted to ml
> before the pull request got in. So I have sent a follow up patch which
> adds the missing
> parts. The patch is here
> 
> http://patches.openembedded.org/patch/6769/
> 
> Please install

Sorry about that, I think things got confused. I've pulled the update,
thanks.

Richard




      reply	other threads:[~2011-06-30 23:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  8:06 [PATCH 0/6] uclibc config cleanup Khem Raj
2011-06-30  8:07 ` [PATCH 1/6] uclibc: Remove redundant machine/arch configs Khem Raj
2011-06-30  8:07 ` [PATCH 2/6] uclibc-config.inc: Fix regexp to determine big-endian arm Khem Raj
2011-06-30  8:07 ` [PATCH 3/6] uclibc.inc: Use ARCH_WANTS_{LITTLE|BIG}_ENDIAN to denote endian Khem Raj
2011-06-30  8:07 ` [PATCH 4/6] uclibc_git.bb: Untether UCLIBC_HAS_FPU from UCLIBC_HAS_FLOATS Khem Raj
2011-06-30  8:07 ` [PATCH 5/6] uclibc: Add UCLIBC_HAS_FLOATS=y to uClibc.distro Khem Raj
2011-06-30  8:07 ` [PATCH 6/6] uclibc: Fix bug exposed by udev 168+ for mips architecture Khem Raj
2011-06-30 22:30 ` [PATCH 0/6] uclibc config cleanup Richard Purdie
2011-06-30 23:36   ` Khem Raj
2011-06-30 23:41     ` Richard Purdie [this message]

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=1309477267.20015.501.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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