Openembedded Core Discussions
 help / color / mirror / Atom feed
From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] commits for yocto.git tree for x32 work
Date: Tue, 12 Jul 2011 12:02:35 -0700	[thread overview]
Message-ID: <cover.1310497097.git.nitin.a.kamble@intel.com> (raw)

From: Nitin A Kamble <nitin.a.kamble@intel.com>

These are commits for yocto tree. I came up with as part of the x32 work. 
I think these commits does not belong in the x32 layer and should go
in the yocto/oecore tree.

The siteinfo.bbclass commit is a hacky way to get the the right siteinfo for 
x32 now. In the future a better solution will be implemented for that purpose.

The following changes since commit 7354fc9213f27aa1b643dbe88070437f1ee4c063:

  insane.bbclass: skip rdepends QA checks for kernel / modules (2011-07-12 15:22:09 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/x32
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/x32

Nitin A Kamble (5):
  siteinfo.bbclass: hack for x32
  udev-172: add a newer version for newer kernel
  runqemu: support qemux32 machine
  kernel.bbclass: fix the broken lines
  glibc: fix false failure

 meta/classes/kernel.bbclass                       |    4 +-
 meta/classes/siteinfo.bbclass                     |    3 +
 meta/recipes-core/glibc/glibc.inc                 |    2 +-
 meta/recipes-core/udev/udev-172/init              |   59 +++++++++
 meta/recipes-core/udev/udev-172/local.rules       |   35 ++++++
 meta/recipes-core/udev/udev-172/permissions.rules |  131 +++++++++++++++++++++
 meta/recipes-core/udev/udev-172/run.rules         |   14 +++
 meta/recipes-core/udev/udev-172/udev.rules        |  116 ++++++++++++++++++
 meta/recipes-core/udev/udev_172.bb                |    6 +
 scripts/qemuimage-testlib                         |    2 +-
 scripts/runqemu                                   |   12 ++-
 scripts/runqemu-internal                          |   25 ++++
 12 files changed, 401 insertions(+), 8 deletions(-)
 create mode 100644 meta/recipes-core/udev/udev-172/init
 create mode 100644 meta/recipes-core/udev/udev-172/local.rules
 create mode 100644 meta/recipes-core/udev/udev-172/permissions.rules
 create mode 100644 meta/recipes-core/udev/udev-172/run.rules
 create mode 100644 meta/recipes-core/udev/udev-172/udev.rules
 create mode 100644 meta/recipes-core/udev/udev_172.bb

-- 
1.7.5.4




             reply	other threads:[~2011-07-13  1:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 19:02 nitin.a.kamble [this message]
2011-07-12 19:02 ` [PATCH 1/5] siteinfo.bbclass: hack for x32 nitin.a.kamble
2011-07-13  6:20   ` Khem Raj
2011-07-13 15:41     ` Kamble, Nitin A
2011-07-14 19:49       ` Khem Raj
2011-07-12 19:02 ` [PATCH 2/5] udev-172: add a newer version for newer kernel nitin.a.kamble
2011-07-13  6:22   ` Khem Raj
2011-07-13  6:59     ` Koen Kooi
2011-07-13 15:43       ` Kamble, Nitin A
2011-07-12 19:02 ` [PATCH 3/5] runqemu: support qemux32 machine nitin.a.kamble
2011-07-13  1:35   ` Bruce Ashfield
2011-07-12 19:02 ` [PATCH 4/5] kernel.bbclass: fix the broken lines nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-12 19:02 ` [PATCH 5/5] glibc: fix false failure nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-13 11:20 ` [PATCH 0/5] commits for yocto.git tree for x32 work Richard Purdie
2011-07-13 14:14   ` Tom Rini
2011-07-13 14:38   ` Khem Raj

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=cover.1310497097.git.nitin.a.kamble@intel.com \
    --to=nitin.a.kamble@intel.com \
    --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