[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200320091341.fglhscnr3sixyzjs@linutronix.de>
Date: Fri, 20 Mar 2020 10:13:41 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: tglx@...utronix.de, arnd@...db.de, balbi@...nel.org,
bhelgaas@...gle.com, davem@...emloft.net,
gregkh@...uxfoundation.org, joel@...lfernandes.org,
kurt.schwemmer@...rosemi.com, kvalo@...eaurora.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
linux-usb@...r.kernel.org, linux-wireless@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, logang@...tatee.com,
mingo@...nel.org, mpe@...erman.id.au, netdev@...r.kernel.org,
oleg@...hat.com, paulmck@...nel.org, peterz@...radead.org,
rdunlap@...radead.org, rostedt@...dmis.org,
torvalds@...ux-foundation.org, will@...nel.org,
Davidlohr Bueso <dbueso@...e.de>
Subject: Re: [PATCH 17/15] rcuwait: Inform rcuwait_wake_up() users if a
wakeup was attempted
On 2020-03-20 01:55:25 [-0700], Davidlohr Bueso wrote:
> Let the caller know if wake_up_process() was actually called or not;
> some users can use this information for ad-hoc. Of course returning
> true does not guarantee that wake_up_process() actually woke anything
> up.
Wouldn't it make sense to return wake_up_process() return value to know
if a change of state occurred or not?
Sebastian
Powered by blists - more mailing lists