From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-handheld][PATCH] linux-kexecboot.inc: hardcode loglevel=3 to keep bootlogo intact
Date: Thu, 15 Sep 2011 00:57:47 +0100 [thread overview]
Message-ID: <201109150057.47810.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1315519241-2950-1-git-send-email-andrea.adami@gmail.com>
On Thursday 08 September 2011 23:00:41 Andrea Adami wrote:
> * debug must be enabled explicitely as it is necessary to add
> * more arguments e.g. earlyprintk and even enable PRINTK and debug
> * in Zaurus defconfigs
This message is a little confusing, is the patch about keeping loglevel=3 for
the bootlogo or the fact that loglevel=3 is insufficient for debugging, or both?
Would you mind expanding the commit message?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-15 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 22:00 [meta-handheld][PATCH] linux-kexecboot.inc: hardcode loglevel=3 to keep bootlogo intact Andrea Adami
2011-09-14 23:57 ` Paul Eggleton [this message]
2011-09-15 20:43 ` [meta-handheld][PATCH v2] " Andrea Adami
2011-09-17 13:56 ` Paul Eggleton
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=201109150057.47810.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=andrea.adami@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.