On Mon, Oct 26, 2015 at 08:04:26PM +0800, Boqun Feng wrote:
> Hi Daniel,
>
> On Tue, Oct 20, 2015 at 09:28:07AM +0200, Daniel Wagner wrote:
> > +
> > +/*
> > + * The thing about the wake_up_state() return value; I think we can ignore
> > it.
> > + *
> > + * If for some reason it would return 0, that means the previously waiting
> > + * task is already running, so it will observe condition true (or has
> > already).
> > + */
> > +void swake_up_locked(struct swait_queue_head *q)
> > +{
> > + struct swait_queue *curr;
> > +
> > + list_for_each_entry(curr, &q->task_list, task_list) {
> > + wake_up_process(curr->task);
> > + list_del_init(&curr->task_list);
> > + break;
>
> Just be curious, what's this break for? Or what's this loop(?) for?
Lazy way of writing: if (!empty) { curr = first-entry;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
