On Wed, 28 Mar 2018 10:36:38 +0800
Dong Jia Shi wrote:
> * Cornelia Huck [2018-03-27 12:01:27 +0200]:
>
> [...]
>
> > > >
> > > > So, basically everything is filled by pfn_array_alloc_pin()?
> > > Yes.
> > >
> > > > Should we expect a clean struct pfn_array handed in by the caller,
> >
On Tue, 27 Mar 2018 11:00:26 +0800
Dong Jia Shi wrote:
> * Cornelia Huck [2018-03-26 15:28:46 +0200]:
>
> > On Wed, 21 Mar 2018 03:08:20 +0100
> > Dong Jia Shi wrote:
> >
> > > This refactors pfn_array_alloc_pin() and also improves it by adding
> > > defensive code in error handling so that
On Wed, 21 Mar 2018 03:08:20 +0100
Dong Jia Shi wrote:
> This refactors pfn_array_alloc_pin() and also improves it by adding
> defensive code in error handling so that calling pfn_array_unpin_free()
> after error return won't lead to problem. This mains does:
> 1. Merge pfn_array_pin() into pfn_a
This refactors pfn_array_alloc_pin() and also improves it by adding
defensive code in error handling so that calling pfn_array_unpin_free()
after error return won't lead to problem. This mains does:
1. Merge pfn_array_pin() into pfn_array_alloc_pin(), since there is no
other user of pfn_array_pi
4 matches
Mail list logo
