Hi,
On Wed, 5 Aug 2020 at 13:32, Tom Rini wrote:
>
> On Wed, Aug 05, 2020 at 09:08:40PM +0200, Heinrich Schuchardt wrote:
> > Am 5. August 2020 21:03:28 MESZ schrieb Tom Rini :
> > >On Wed, Aug 05, 2020 at 12:56:17PM -0600, Simon Glass wrote:
> > >> Hi Tom,
> > >>
> > >> On Wed, 5 Aug 2020 at 12:
On Wed, Aug 05, 2020 at 09:08:40PM +0200, Heinrich Schuchardt wrote:
> Am 5. August 2020 21:03:28 MESZ schrieb Tom Rini :
> >On Wed, Aug 05, 2020 at 12:56:17PM -0600, Simon Glass wrote:
> >> Hi Tom,
> >>
> >> On Wed, 5 Aug 2020 at 12:37, Tom Rini wrote:
> >> >
> >> > On Wed, Aug 05, 2020 at 08:31
Am 5. August 2020 21:03:28 MESZ schrieb Tom Rini :
>On Wed, Aug 05, 2020 at 12:56:17PM -0600, Simon Glass wrote:
>> Hi Tom,
>>
>> On Wed, 5 Aug 2020 at 12:37, Tom Rini wrote:
>> >
>> > On Wed, Aug 05, 2020 at 08:31:55PM +0200, Heinrich Schuchardt
>wrote:
>> > > On 05.08.20 14:56, Tom Rini wrote:
On Wed, Aug 05, 2020 at 12:56:17PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Wed, 5 Aug 2020 at 12:37, Tom Rini wrote:
> >
> > On Wed, Aug 05, 2020 at 08:31:55PM +0200, Heinrich Schuchardt wrote:
> > > On 05.08.20 14:56, Tom Rini wrote:
> > > > On Wed, Aug 05, 2020 at 02:54:05PM +0200, Heinrich
Hi Tom,
On Wed, 5 Aug 2020 at 12:37, Tom Rini wrote:
>
> On Wed, Aug 05, 2020 at 08:31:55PM +0200, Heinrich Schuchardt wrote:
> > On 05.08.20 14:56, Tom Rini wrote:
> > > On Wed, Aug 05, 2020 at 02:54:05PM +0200, Heinrich Schuchardt wrote:
> > >> On 05.08.20 14:18, Tom Rini wrote:
> > >>> On Sun,
On Wed, Aug 05, 2020 at 08:31:55PM +0200, Heinrich Schuchardt wrote:
> On 05.08.20 14:56, Tom Rini wrote:
> > On Wed, Aug 05, 2020 at 02:54:05PM +0200, Heinrich Schuchardt wrote:
> >> On 05.08.20 14:18, Tom Rini wrote:
> >>> On Sun, Jul 26, 2020 at 08:27:35PM -0600, Simon Glass wrote:
> >>>
>
On 05.08.20 14:56, Tom Rini wrote:
> On Wed, Aug 05, 2020 at 02:54:05PM +0200, Heinrich Schuchardt wrote:
>> On 05.08.20 14:18, Tom Rini wrote:
>>> On Sun, Jul 26, 2020 at 08:27:35PM -0600, Simon Glass wrote:
>>>
At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
(be
On Wed, Aug 05, 2020 at 02:54:05PM +0200, Heinrich Schuchardt wrote:
> On 05.08.20 14:18, Tom Rini wrote:
> > On Sun, Jul 26, 2020 at 08:27:35PM -0600, Simon Glass wrote:
> >
> >> At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
> >> (before log.h inclusion) causes _log() to
On 05.08.20 14:18, Tom Rini wrote:
> On Sun, Jul 26, 2020 at 08:27:35PM -0600, Simon Glass wrote:
>
>> At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
>> (before log.h inclusion) causes _log() to be executed for every log()
>> call, regardless of the build- or run-time logg
On Sun, Jul 26, 2020 at 08:27:35PM -0600, Simon Glass wrote:
> At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
> (before log.h inclusion) causes _log() to be executed for every log()
> call, regardless of the build- or run-time logging level.
>
> However there is no guara
Hi Heinrich,
On Mon, 27 Jul 2020 at 00:15, Heinrich Schuchardt wrote:
>
> On 7/27/20 4:27 AM, Simon Glass wrote:
> > At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
> > (before log.h inclusion) causes _log() to be executed for every log()
> > call, regardless of the build
On 7/27/20 4:27 AM, Simon Glass wrote:
> At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
> (before log.h inclusion) causes _log() to be executed for every log()
> call, regardless of the build- or run-time logging level.
>
> However there is no guarantee that the log record
At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
(before log.h inclusion) causes _log() to be executed for every log()
call, regardless of the build- or run-time logging level.
However there is no guarantee that the log record will actually be
displayed. If the current log
13 matches
Mail list logo