From: Greg KH <gregkh@linuxfoundation.org>
To: "Zhang, Qiang" <Qiang.Zhang@windriver.com>
Cc: "balbi@kernel.org" <balbi@kernel.org>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 回复: [PATCH v3] usb: gadget: function: fix missing spinlock in f_uac1_legacy
Date: Tue, 7 Jul 2020 08:51:39 +0200 [thread overview]
Message-ID: <20200707065139.GA5233@kroah.com> (raw)
In-Reply-To: <BYAPR11MB26323A0A7687EC2CE3C9E17FFF660@BYAPR11MB2632.namprd11.prod.outlook.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Tue, Jul 07, 2020 at 02:28:36AM +0000, Zhang, Qiang wrote:
> Hi Greg KH
> In the early submission:
> "commit id c6994e6f067cf0fc4c6cca3d164018b1150916f8" which add USB Audio Gadget driver "
> the "audio->play_queue" was protected from "audio->lock"
> spinlock in "playback_work" func, But in "f_audio_out_ep_complete" func
> there is no protection for the operation of this "audio->play_queue". there
> are missing spinlock, Fix tags should add up here commit？
I really do not understand what you are asking here, sorry.
greg k-h
next prev parent reply other threads:[~2020-07-07 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 12:40 [PATCH v3] usb: gadget: function: fix missing spinlock in f_uac1_legacy qiang.zhang
2020-07-06 19:55 ` Greg KH
2020-07-07 2:28 ` 回复: " Zhang, Qiang
2020-07-07 6:51 ` Greg KH [this message]
2020-07-07 8:35 ` Sergei Shtylyov
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=20200707065139.GA5233@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Qiang.Zhang@windriver.com \
--cc=balbi@kernel.org \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox