Re: aprint_* used outside autoconfiguration step

[Jason Thorpe]

> On Feb 19, 2019, at 1:44 PM, matthew green <m...@eterna.com.au> wrote:
> 
> can we eliminate this one entirely while we are at it?  it's
> unfortunately used a *lot*.

We should probably just get rid of aprint_naive(), too.

> 
>>      2. We don't have a non-autoconfig-related family of printf
>>         calls to handle errors outside autoconfiguration.
> 
> we have device_printf(9).  perhaps a device_printf_error()?
> 
> 
> .mrg.

-- thorpej