From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Artur Petrosyan <Arthur.Petrosyan@synopsys.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
linux-usb@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
John Youn <John.Youn@synopsys.com>,
Paul Zimmerman <paulz@synopsys.com>,
stable@vger.kernel.org, #@synopsys.com, 4.18@synopsys.com,
5.2@synopsys.com, Felipe Balbi <balbi@ti.com>,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH 0/3] usb: dwc2: Fix power saving general issues.
Date: Fri, 26 Mar 2021 14:32:52 +0100 [thread overview]
Message-ID: <YF3ihMf3cHESK0cq@kroah.com> (raw)
In-Reply-To: <20210326102400.359EFA005C@mailhost.synopsys.com>
On Fri, Mar 26, 2021 at 02:23:58PM +0400, Artur Petrosyan wrote:
> This patch set is part of multiple series and is
> continuation of the "usb: dwc2: Fix and improve
> power saving modes" patch set.
> (Patch set link: https://marc.info/?l=linux-usb&m=160379622403975&w=2).
>
> The patches that were included in the "usb: dwc2:
> Fix and improve power saving modes" which was submitted
> earlier was too large and needed to be split up into
> smaller patch sets. So this is the first series in the
> whole power saving mode fixes.
>
> Each remaining patch set have dependency on previous set
> and will be submitted after each of them are integrated.
>
> The series includes the following patch sets with multiple patches
> by below order.
> 1. usb: dwc2: Fix power saving general issues.
> 2. usb: dwc2: Fix Partial Power down issues.
> 3. usb: dwc2: Add clock gating support.
> 4. usb: dwc2: Fix Hibernation issues
You only sent 3 patches, not 4.
So this makes no sense to me, what am I supposed to do?
confused,
greg k-h
next prev parent reply other threads:[~2021-03-26 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 10:23 [PATCH 0/3] usb: dwc2: Fix power saving general issues Artur Petrosyan
2021-03-26 13:32 ` Greg Kroah-Hartman [this message]
2021-03-26 13:45 ` Artur Petrosyan
2021-03-26 14:10 ` Greg Kroah-Hartman
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=YF3ihMf3cHESK0cq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=#@synopsys.com \
--cc=4.18@synopsys.com \
--cc=5.2@synopsys.com \
--cc=Arthur.Petrosyan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=balbi@kernel.org \
--cc=balbi@ti.com \
--cc=dianders@chromium.org \
--cc=kever.yang@rock-chips.com \
--cc=linux-usb@vger.kernel.org \
--cc=paulz@synopsys.com \
--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