All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Billauer <eli.billauer@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	hdegoede@redhat.com, oneukum@suse.de
Subject: Re: [PATCH v4] usb: core: Solve race condition in anchor cleanup functions
Date: Thu, 30 Jul 2020 18:14:15 +0300	[thread overview]
Message-ID: <5F22E3C7.1030305@gmail.com> (raw)
In-Reply-To: <20200730144614.GB1604718@rowland.harvard.edu>

On 30/07/20 17:46, Alan Stern wrote:
> This loop ought to have a cpu_relax() somewhere, probably here.  Same
> for the other two functions.  Otherwise this looks okay to me.
>    
This function isn't so well documented. Does it go with an include file? 
asm/processor.h, for example? Or just add the call?

Thanks,
    Eli

  reply	other threads:[~2020-07-30 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 14:18 [PATCH v4] usb: core: Solve race condition in anchor cleanup functions eli.billauer
2020-07-30 14:46 ` Alan Stern
2020-07-30 15:14   ` Eli Billauer [this message]
2020-07-30 15:28     ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5F22E3C7.1030305@gmail.com \
    --to=eli.billauer@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.