On Fri, Dec 11, 2015 at 08:01:39AM -0700, Eric Blake wrote:
> On 12/10/2015 05:11 PM, David Gibson wrote:
> > The spapr_alloc_htab() and spapr_reset_htab() functions currently handle
> > all errors with error_setg(&error_abort, ...). That's correct for
> > spapr_reset_htab() - if anything goes wro
On Fri, Dec 11, 2015 at 02:10:40PM +0530, Bharata B Rao wrote:
> On Fri, Dec 11, 2015 at 5:41 AM, David Gibson
> wrote:
> > The spapr_alloc_htab() and spapr_reset_htab() functions currently handle
> > all errors with error_setg(&error_abort, ...). That's correct for
> > spapr_reset_htab() - if an
On 12/10/2015 05:11 PM, David Gibson wrote:
> The spapr_alloc_htab() and spapr_reset_htab() functions currently handle
> all errors with error_setg(&error_abort, ...). That's correct for
> spapr_reset_htab() - if anything goes wrong there, there's really nothing
> we can do about it. For spapr_al
On Fri, Dec 11, 2015 at 5:41 AM, David Gibson
wrote:
> The spapr_alloc_htab() and spapr_reset_htab() functions currently handle
> all errors with error_setg(&error_abort, ...). That's correct for
> spapr_reset_htab() - if anything goes wrong there, there's really nothing
> we can do about it. Fo
The spapr_alloc_htab() and spapr_reset_htab() functions currently handle
all errors with error_setg(&error_abort, ...). That's correct for
spapr_reset_htab() - if anything goes wrong there, there's really nothing
we can do about it. For spapr_alloc_htab() &error_fatal would make more
sense, since