From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Fri, 28 Jun 2019 07:55:03 -0600
Subject: [U-Boot] [PATCH 1/1] trace: make call depth limit customizable
In-Reply-To: <CAPnjgZ3970MHfgcc69SVDyp6Omk-FKELOwFDha5zYR4EVG7o6A@mail.gmail.com>
References: <20190602113009.32764-1-xypron.glpk@gmx.de>
 <CAPnjgZ3970MHfgcc69SVDyp6Omk-FKELOwFDha5zYR4EVG7o6A@mail.gmail.com>
Message-ID: <CAPnjgZ3LKs56onFK9fssOhOMJwv_S7MmSpTUF-CJiFaO0P=sLw@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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!