From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] trace: make call depth limit customizable
Date: Fri, 28 Jun 2019 07:55:03 -0600 [thread overview]
Message-ID: <CAPnjgZ3LKs56onFK9fssOhOMJwv_S7MmSpTUF-CJiFaO0P=sLw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ3970MHfgcc69SVDyp6Omk-FKELOwFDha5zYR4EVG7o6A@mail.gmail.com>
On Sat, 22 Jun 2019 at 13:10, Simon Glass <sjg@chromium.org> wrote:
>
> On Sun, 2 Jun 2019 at 12:30, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >
> > Up to now we had hard coded values for the call depth up to which trace
> > records are created: 200 for early tracing, 15 thereafter. UEFI
> > applications reach a call depth of 80 or above.
> >
> > Provide customizing settings for the call trace depth limit and the early
> > call trace depth limit. Use the old values as defaults.
> >
> > Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> > ---
> > lib/Kconfig | 15 +++++++++++++++
> > lib/trace.c | 4 ++--
> > 2 files changed, 17 insertions(+), 2 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot-dm/next, thanks!
prev parent reply other threads:[~2019-06-28 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 11:30 [U-Boot] [PATCH 1/1] trace: make call depth limit customizable Heinrich Schuchardt
2019-06-22 19:10 ` Simon Glass
2019-06-28 13:55 ` Simon Glass [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='CAPnjgZ3LKs56onFK9fssOhOMJwv_S7MmSpTUF-CJiFaO0P=sLw@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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.