From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: linux-pm@vger.kernel.org
Cc: linux-i2c@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linux-renesas-soc@vger.kernel.org, linux-usb@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: [PATCH 0/3] PM: Renesas: Remove dummy runtime PM callbacks
Date: Wed, 24 Oct 2018 16:51:31 +0300 [thread overview]
Message-ID: <20181024135134.28456-1-jarkko.nikula@linux.intel.com> (raw)
I noticed these independent Renesas drivers have needless dummy runtime
PM callbacks. I don't have the HW so only build tested.
Patches can be applied independently to their own subsystems. I wanted to
send them together if some of them gets Tested-by or sees a regression.
Jarkko Nikula (3):
i2c: sh_mobile: Remove dummy runtime PM callbacks
net: ethernet: Remove dummy runtime PM callbacks from Renesas drivers
usb: renesas_usbhs: Remove dummy runtime PM callbacks
drivers/i2c/busses/i2c-sh_mobile.c | 18 ------------------
drivers/net/ethernet/renesas/ravb_main.c | 13 -------------
drivers/net/ethernet/renesas/sh_eth.c | 13 -------------
drivers/usb/renesas_usbhs/common.c | 14 --------------
4 files changed, 58 deletions(-)
--
2.19.1
next reply other threads:[~2018-10-24 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 13:51 Jarkko Nikula [this message]
2018-10-24 13:51 ` [PATCH 1/3] i2c: sh_mobile: Remove dummy runtime PM callbacks Jarkko Nikula
2018-10-28 22:22 ` Wolfram Sang
2018-10-24 13:51 ` [PATCH 2/3] net: ethernet: Remove dummy runtime PM callbacks from Renesas drivers Jarkko Nikula
2018-10-24 17:44 ` Sergei Shtylyov
2018-10-25 22:54 ` Wolfram Sang
2018-10-24 13:51 ` [PATCH 3/3] usb: renesas_usbhs: Remove dummy runtime PM callbacks Jarkko Nikula
2018-10-25 2:45 ` Yoshihiro Shimoda
2018-10-25 22:57 ` Wolfram Sang
2018-10-26 2:09 ` Yoshihiro Shimoda
2018-10-24 14:22 ` [PATCH 0/3] PM: Renesas: " Wolfram Sang
2018-10-25 0:20 ` Wolfram Sang
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=20181024135134.28456-1-jarkko.nikula@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=davem@davemloft.net \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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).