Re: [PATCH 1/1] sandbox: fix sandbox_reset()

2021-07-04 Thread Simon Glass
On Wed, 12 May 2021 at 10:39, Heinrich Schuchardt wrote: > > state_uninit() and dm_uninit() are mutually exclusive: > > state_uninit() prints via drivers. So it cannot be executed after > dm_uninit(). > > dm_uninit() requires memory. So it cannot be executed after state_uninit() > which releases a

Re: [PATCH 1/1] sandbox: fix sandbox_reset()

2021-05-15 Thread Simon Glass
On Wed, 12 May 2021 at 10:39, Heinrich Schuchardt wrote: > > state_uninit() and dm_uninit() are mutually exclusive: > > state_uninit() prints via drivers. So it cannot be executed after > dm_uninit(). > > dm_uninit() requires memory. So it cannot be executed after state_uninit() > which releases a

Re: [PATCH 1/1] sandbox: fix sandbox_reset()

2021-05-12 Thread Vincent Stehlé
On Wed, May 12, 2021 at 06:38:51PM +0200, Heinrich Schuchardt wrote: > state_uninit() and dm_uninit() are mutually exclusive: > > state_uninit() prints via drivers. So it cannot be executed after > dm_uninit(). > > dm_uninit() requires memory. So it cannot be executed after state_uninit() > which

[PATCH 1/1] sandbox: fix sandbox_reset()

2021-05-12 Thread Heinrich Schuchardt
state_uninit() and dm_uninit() are mutually exclusive: state_uninit() prints via drivers. So it cannot be executed after dm_uninit(). dm_uninit() requires memory. So it cannot be executed after state_uninit() which releases all memory. Just skip dm_uninit() when resetting the sandbox. We will wa