From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Holger Freyther <holger@freyther.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: Do not chdir to /boot before running update-alternatives
Date: Mon, 22 Oct 2012 16:51:21 +0100 [thread overview]
Message-ID: <1350921081.22340.1.camel@ted> (raw)
In-Reply-To: <loom.20121021T094018-148@post.gmane.org>
On Sun, 2012-10-21 at 07:42 +0000, Holger Freyther wrote:
> Holger Hans Peter Freyther <holger@...> writes:
>
> >
> > The symlink from uImage-3... to uImage is not created at image creation
> > time and not properly update on kernel upgrades. This is fixed by removing
> > the chdir. The other users of update-alternative do not change the directory
> > before calling it.
>
> Hi,
>
> this patch has not been merged, nor has it received any comments. The symlink
> creation for uImage is broken right now and I would be very happy if it could
> be fixed.
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-10-22 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 18:01 [PATCH] kernel.bbclass: Do not chdir to /boot before running update-alternatives Holger Hans Peter Freyther
2012-10-21 7:42 ` Holger Freyther
2012-10-22 15:51 ` 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=1350921081.22340.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=holger@freyther.de \
--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