From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linyu Yuan <quic_linyyuan@quicinc.com>
Cc: Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, Jack Pham <jackp@quicinc.com>
Subject: Re: [PATCH v12 0/4] usb: gadget: configfs: add some trace event
Date: Fri, 22 Oct 2021 11:19:41 +0200 [thread overview]
Message-ID: <YXKCLeqPO07TmKZ5@kroah.com> (raw)
In-Reply-To: <1634649997-28745-1-git-send-email-quic_linyyuan@quicinc.com>
On Tue, Oct 19, 2021 at 09:26:33PM +0800, Linyu Yuan wrote:
> this series make some minor change to gadget configfs and
> add some important trace event from configfs layer.
>
> follow suggestion from Felipe Balbi in link below,
> https://lore.kernel.org/linux-usb/1629777281-30188-1-git-send-email-quic_linyyuan@quicinc.com/
I've applied the first 2 patches here, as they are nice "cleanup"
changes. But I had a problem with patch 3, and I need others to help
review patch 4 so I can not take them at this point in time yet. Feel
free to rebase the remaining patches on my tree so you no longer have to
send the first 2 anymore.
thanks,
greg k-h
prev parent reply other threads:[~2021-10-22 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 13:26 [PATCH v12 0/4] usb: gadget: configfs: add some trace event Linyu Yuan
2021-10-19 13:26 ` [PATCH v12 1/4] usb: gadget: configfs: add cfg_to_gadget_info() helper Linyu Yuan
2021-10-19 13:26 ` [PATCH v12 2/4] usb: gadget: configfs: change config attributes file operation Linyu Yuan
2021-10-19 13:26 ` [PATCH v12 3/4] usb: gadget: configfs: use gi->lock to protect write operation Linyu Yuan
2021-10-22 9:16 ` Greg Kroah-Hartman
2021-10-19 13:26 ` [PATCH v12 4/4] usb: gadget: add configfs trace events Linyu Yuan
2021-10-22 9:20 ` Greg Kroah-Hartman
2021-10-22 9:43 ` Linyu Yuan (QUIC)
2021-10-22 11:37 ` Greg Kroah-Hartman
2021-10-22 9:19 ` Greg Kroah-Hartman [this message]
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=YXKCLeqPO07TmKZ5@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=jackp@quicinc.com \
--cc=linux-usb@vger.kernel.org \
--cc=quic_linyyuan@quicinc.com \
/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