From: Frank Li <Frank.li@nxp.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Peter Chen <peter.chen@kernel.org>,
imx@lists.linux.dev, Pawel Laszczak <pawell@cadence.com>,
Roger Quadros <rogerq@kernel.org>,
Aswath Govindraju <a-govindraju@ti.com>,
"open list:CADENCE USB3 DRD IP DRIVER"
<linux-usb@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] usb: cdns3: skip set TRB_IOC when usb_request: no_interrupt is true
Date: Mon, 27 Nov 2023 11:07:40 -0500 [thread overview]
Message-ID: <ZWS+zLhtleUXuBOH@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <2023112748-coveted-enunciate-cf13@gregkh>
On Mon, Nov 27, 2023 at 03:52:13PM +0000, Greg KH wrote:
> On Mon, Nov 27, 2023 at 10:28:57AM -0500, Frank Li wrote:
> > On Tue, Oct 31, 2023 at 04:45:21PM +0800, Peter Chen wrote:
> > > On 23-10-27 14:39:19, Frank Li wrote:
> > > > No completion irq is needed if no_interrupt is true. Needn't set TRB_IOC
> > > > at this case.
> > > >
> > > > Check usb_request: no_interrupt and set/skip TRB_IOC in
> > > > cdns3_ep_run_transfer().
> > > >
> > > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > >
> > > Acked-by: Peter Chen <peter.chen@kernel.org>
> >
> > @Greg:
> > ping
>
> What are you needing from me here? Blind pings do not provide any
> context :(
Sorry, I just saw it is already in linux-next tree. Generally, I received a
"applied"'s email. So I have not check linux-next tree before send it.
Frank
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2023-11-27 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 18:39 [PATCH 1/1] usb: cdns3: skip set TRB_IOC when usb_request: no_interrupt is true Frank Li
2023-10-31 8:45 ` Peter Chen
2023-11-27 15:28 ` Frank Li
2023-11-27 15:52 ` Greg KH
2023-11-27 16:07 ` Frank Li [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=ZWS+zLhtleUXuBOH@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=a-govindraju@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=peter.chen@kernel.org \
--cc=rogerq@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 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.