From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Sun, 31 May 2020 10:09:40 -0600
Subject: printk
In-Reply-To: <95cadde5-1aeb-392f-9933-5965dc3af1e8@gmx.de>
References: <95cadde5-1aeb-392f-9933-5965dc3af1e8@gmx.de>
Message-ID: <CAPnjgZ1CaAyBtKNE0xfwEOwzAtHdHkmU4D9+R1muakg7WPEcTw@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

Hi Heinrich,

On Sun, 31 May 2020 at 09:34, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
> Hello Simon,
>
> in some drivers we use printk() which is restricted by CONFIG_LOGLEVEL
> and translates to printf().
>
> Shouldn't printk() be translated to log() instead?
>
> CONFIG_LOGLEVEL probably should better be renamed to
> CONFIG_PRINTK_LOGLEVEL to avoid confusion.
>
> And those different levels like KERN_WARNING should probably be properly
> defined to translate into out log levels.

Yes definitely. I have been thinking about those things for a while,
not to mention dev_err() and friends.

Regards,
Simon