On 5/27/20 2:19 AM, Cornelia Huck wrote: > On Tue, 26 May 2020 15:39:22 -0400 > Eric Farman <farman@xxxxxxxxxxxxx> wrote: > >> On 5/8/20 6:55 AM, Cornelia Huck wrote: >>> On Fri, 17 Apr 2020 12:33:18 -0400 >>> Eric Farman <farman@xxxxxxxxxxxxx> wrote: >>> >>>> On 4/7/20 7:16 AM, Cornelia Huck wrote: >>>>> Interacting with the I/O and the async regions can yield a number >>>>> of errors, which had been undocumented so far. These are part of >>>>> the api, so remedy that. >>>> >>>> (Makes a note to myself, to do the same for the schib/crw regions we're >>>> adding for channel path handling.) >>> >>> Yes, please :) I plan to merge this today, so you can add a patch on >>> top. >> >> I finally picked this up and realized that the io and async regions both >> document the return codes that would be stored in a field within their >> respective regions. The schib/crw regions don't have any such field, so >> the only values to be documented are the ones that the .read callback >> itself returns. What obvious thing am I missing? > > The fact that you are right :) > > No need to do anything, I might have spread my own confusion here ;) > Oh, good. I was worried vacation was too long/short. :) Thanks for confirming; will get back to the other things on the list instead.
