Hi Tom,
On Sun, 14 Mar 2021 at 12:33, Tom Rini wrote:
>
> On Wed, Jan 20, 2021 at 08:10:57PM -0700, Simon Glass wrote:
>
> > At present if logging not enabled, log_info() becomes a nop. But we want
> > log output at the 'info' level to be akin to printf(). Update the macro to
> > pass the output
On Wed, Jan 20, 2021 at 08:10:57PM -0700, Simon Glass wrote:
> At present if logging not enabled, log_info() becomes a nop. But we want
> log output at the 'info' level to be akin to printf(). Update the macro to
> pass the output straight to printf() in this case.
>
> This mimics the behaviour f
Hi Sean,
On Thu, 4 Feb 2021 at 18:28, Sean Anderson wrote:
>
> On 1/20/21 10:10 PM, Simon Glass wrote:
> > At present if logging not enabled, log_info() becomes a nop. But we want
> > log output at the 'info' level to be akin to printf(). Update the macro to
> > pass the output straight to printf
On 1/20/21 10:10 PM, Simon Glass wrote:
At present if logging not enabled, log_info() becomes a nop. But we want
log output at the 'info' level to be akin to printf(). Update the macro to
pass the output straight to printf() in this case.
This mimics the behaviour for the log_...() macros like l
At present if logging not enabled, log_info() becomes a nop. But we want
log output at the 'info' level to be akin to printf(). Update the macro to
pass the output straight to printf() in this case.
This mimics the behaviour for the log_...() macros like log_debug() and
log_info(), so we can drop
5 matches
Mail list logo