From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-handheld] [PATCH 0/3] [zaurus] rely on devtmpfs in kernel
Date: Mon, 16 Jan 2012 16:16:43 +0000 [thread overview]
Message-ID: <2636293.vMRAZY5Chk@helios> (raw)
In-Reply-To: <1326672731-7001-1-git-send-email-andrea.adami@gmail.com>
On Monday 16 January 2012 01:12:08 Andrea Adami wrote:
> * No need for static device tables when using devtmpfs.
> * The /dev directory must exist, though: kexecboot provides it
> * Bump to latest kexecboot to manage the empty /dev and
> * increase PR of linux-kexecboot to keep in synch.
>
> Andrea Adami (3):
> kexecboot_git: move to 8f1d3cc3d9c650c6a6c88f83071185d6ee0ef9c7
> linux-kexecboot: bump INC_PR to follow kexecboot upgrade
> zaurus.inc: don't install device nodes, rely on devtmpfs
>
> conf/machine/include/zaurus.inc | 2 ++
> recipes-bsp/kexecboot/kexecboot-klibc_git.bb | 4 ++--
> recipes-bsp/kexecboot/kexecboot.inc | 3 ++-
> recipes-bsp/kexecboot/kexecboot_git.bb | 4 ++--
> recipes-kernel/linux/linux-kexecboot.inc | 2 +-
> 5 files changed, 9 insertions(+), 6 deletions(-)
Merged to meta-handheld master, thanks!
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-01-16 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 0:12 [meta-handheld] [PATCH 0/3] [zaurus] rely on devtmpfs in kernel Andrea Adami
2012-01-16 0:12 ` [meta-handheld] [PATCH 1/3] kexecboot_git: move to 8f1d3cc3d9c650c6a6c88f83071185d6ee0ef9c7 Andrea Adami
2012-01-16 0:12 ` [meta-handheld] [PATCH 2/3] linux-kexecboot: bump INC_PR to follow kexecboot upgrade Andrea Adami
2012-01-16 0:12 ` [meta-handheld] [PATCH 3/3] zaurus.inc: don't install device nodes, rely on devtmpfs Andrea Adami
2012-01-16 16:16 ` Paul Eggleton [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=2636293.vMRAZY5Chk@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@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