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" <linux-usb@vger.kernel.org>,
John Youn <John.Youn@synopsys.com>
Subject: Re: [PATCH 1/3] usb: dwc2: Add default param to control power optimization.
Date: Fri, 26 Mar 2021 14:30:40 +0100 [thread overview]
Message-ID: <YF3iAGC5NjMxtwOP@kroah.com> (raw)
In-Reply-To: <ce789dca-82ae-0800-7577-2ea0d4c33955@synopsys.com>
On Wed, Mar 24, 2021 at 04:44:31PM +0000, Artur Petrosyan wrote:
> Hi Greg,
>
> On 3/23/2021 15:24, Greg Kroah-Hartman wrote:
> > On Thu, Mar 18, 2021 at 10:12:46AM +0400, Artur Petrosyan wrote:
> >> - Added a default param "power_saving" to enable or
> >> disable hibernation or partial power down features.
> >>
> >> - Printed hibernation param in hw_params_show and
> >> power_saving param in params_show.
> >
> > This says what you are doing, but not _why_ you are doing this. Why is
> > this needed at all?
> >
> > Please read the documentation for how to write a good changelog text for
> > when you resubmit this series.
>
> Thank you for your reply. I have corrected changelog of the patch
> according the documentation. Will submit in series.
>
> >
> > Also note that the emails were not "threaded", was that on purpose?
> Yes, the patches that were included in the "usb: dwc2: Fix and improve
> power saving modes" which was submitted earlier were too large and
> needed to be split up into smaller patches.
> We had a discussion about that with Felipe Balbi earlier. Here is the
> link to the discussion thread
> (https://marc.info/?l=linux-usb&m=160379651904064&w=2)
> So I did the split and obviously the cover letter and the subject were
> changed therefor I have submitted the updates with this thread and
> mentioned in the cover letter that these are continuation of the
> previous patch set that was too large.
No, I mean you are not "threading" your emails so that they show up as
one after another all in the same email "thread". Please use
git-send-email to do this, or some other tool.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-26 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210318061247.B2EACA005D@mailhost.synopsys.com>
2021-03-23 11:24 ` [PATCH 1/3] usb: dwc2: Add default param to control power optimization Greg Kroah-Hartman
2021-03-24 16:44 ` Artur Petrosyan
2021-03-26 13:30 ` Greg Kroah-Hartman [this message]
[not found] <20210326102424.7AE5BA005D@mailhost.synopsys.com>
2021-03-26 13:32 ` 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=YF3iAGC5NjMxtwOP@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Arthur.Petrosyan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=balbi@kernel.org \
--cc=linux-usb@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 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.