From: Greg KH <gregkh@linuxfoundation.org>
To: Wesley Cheng <wcheng@codeaurora.org>
Cc: robh+dt@kernel.org, agross@kernel.org,
bjorn.andersson@linaro.org, balbi@kernel.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
jackp@codeaurora.org, fntoth@gmail.com
Subject: Re: [PATCH v11 0/5] Re-introduce TX FIFO resize for larger EP bursting
Date: Fri, 2 Jul 2021 07:04:36 +0200 [thread overview]
Message-ID: <YN6eZIuIUjjpP/56@kroah.com> (raw)
In-Reply-To: <1625043642-29822-1-git-send-email-wcheng@codeaurora.org>
On Wed, Jun 30, 2021 at 02:00:37AM -0700, Wesley Cheng wrote:
> Changes in V11:
> - Added a DWC3 controller revision check to use a different calculation, based
> on Ferry's testing.
> - Removed descriptor loop in configfs, and utilize the fact that the ep->claimed
> parameter is still valid as ep_autoconf_reset() isn't called at the time of
> check_config()
> - Fix compilation errors if CONFIG_OF is not defined
> - Removed patch to add stubs for of_add_property()
Still breaks the build :(
prev parent reply other threads:[~2021-07-02 5:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 9:00 [PATCH v11 0/5] Re-introduce TX FIFO resize for larger EP bursting Wesley Cheng
2021-06-30 9:00 ` [PATCH v11 1/5] usb: gadget: udc: core: Introduce check_config to verify USB configuration Wesley Cheng
2021-07-02 5:00 ` Greg KH
2021-07-02 8:00 ` Wesley Cheng
2021-06-30 9:00 ` [PATCH v11 2/5] usb: gadget: configfs: Check USB configuration before adding Wesley Cheng
2021-06-30 9:00 ` [PATCH v11 3/5] usb: dwc3: Resize TX FIFOs to meet EP bursting requirements Wesley Cheng
2021-06-30 9:00 ` [PATCH v11 4/5] usb: dwc3: dwc3-qcom: Enable tx-fifo-resize property by default Wesley Cheng
2021-07-01 1:09 ` kernel test robot
2021-07-02 5:06 ` Greg KH
2021-07-02 8:10 ` Wesley Cheng
2021-07-02 8:19 ` Greg KH
2021-06-30 9:00 ` [PATCH v11 5/5] dt-bindings: usb: dwc3: Update dwc3 TX fifo properties Wesley Cheng
2021-07-02 5:04 ` Greg KH [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=YN6eZIuIUjjpP/56@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fntoth@gmail.com \
--cc=jackp@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wcheng@codeaurora.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;
as well as URLs for NNTP newsgroup(s).