On Thu, Mar 19, 2020 at 11:09:45PM -0400, Steven Rostedt wrote: > On Thu, 19 Mar 2020 19:49:43 -0700 > "Paul E. McKenney" <paulmck@xxxxxxxxxx> wrote: > > > > The current setup is very convenient for the use cases thus far. It > > > allows the function to say "Yeah, I was called, but I couldn't do > > > anything", thus allowing the caller to make exactly one check to know > > > that corrective action is required. > > > > And here is another use case that led me to take this approach. > > The trc_inspect_reader_notrunning() function in the patch below is passed > > to try_invoke_on_locked_down_task() whose caller can continue testing > > just the return value from try_invoke_on_locked_down_task() to work out > > what to do next. > > > > Thoughts? Other use cases? > > Note, I made this comment before looking at the use cases in the later > patches. I was looking at it for a more generic purpose, but I'm not > sure there is one. > > It's fine as is for now. Sounds good, and again thank you for looking this over! Thanx, Paul