From: Greg KH <gregkh@linuxfoundation.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: balbi@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, cristian.birsan@microchip.com,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] usb: gadget: at91_udc: stop using legacy pm ops
Date: Tue, 26 Jul 2022 19:11:39 +0200 [thread overview]
Message-ID: <YuAgSxsJufJoIfCP@kroah.com> (raw)
In-Reply-To: <20220726095948.1809038-1-claudiu.beznea@microchip.com>
On Tue, Jul 26, 2022 at 12:59:47PM +0300, Claudiu Beznea wrote:
> Stop using legacy PM ops and switch using dev_pm_ops.
That says what you did, but not why you are doing this.
Please read the kernel documentation for how to write a good kernel
changelog and resubmit.
thanks,
greg k-h
prev parent reply other threads:[~2022-07-26 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 9:59 [PATCH 1/2] usb: gadget: at91_udc: stop using legacy pm ops Claudiu Beznea
2022-07-26 9:59 ` [PATCH 2/2] usb: gadget: udc: atmel: remove #ifdef CONFIG_PM_SLEEP Claudiu Beznea
2022-07-26 17:11 ` 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=YuAgSxsJufJoIfCP@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=balbi@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=cristian.birsan@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.ferre@microchip.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;
as well as URLs for NNTP newsgroup(s).