From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: pull-request: can-next 2017-05-18
Date: Thu, 18 May 2017 10:56:31 +0200 [thread overview]
Message-ID: <28d10e0b-bc7a-de01-8fd7-9eb3c1f70f3c@pengutronix.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1493 bytes --]
Hello David,
this is a pull request of 4 patches for net-next/master.
All 4 patches are by Quentin Schulz, they add deep deep Suspend/Resume
support to the m_can driver.
regards,
Marc
---
The following changes since commit 1fc4d180b3c6bed0e7f5160bcd553aec89594962:
Merge branch 'phy-marvell-cleanups' (2017-05-17 16:27:52 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-4.13-20170518
for you to fetch changes up to d14ccea0e71a55ad02bf4e1cb378bbece282d5cf:
can: m_can: add deep Suspend/Resume support (2017-05-18 10:32:48 +0200)
----------------------------------------------------------------
linux-can-next-for-4.13-20170518
----------------------------------------------------------------
Quentin Schulz (4):
can: m_can: move Message RAM initialization to function
can: m_can: make m_can_start and m_can_stop symmetric
can: m_can: factorize clock gating and ungating
can: m_can: add deep Suspend/Resume support
drivers/net/can/m_can/m_can.c | 87 ++++++++++++++++++++++++++-----------------
1 file changed, 53 insertions(+), 34 deletions(-)
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2017-05-18 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=28d10e0b-bc7a-de01-8fd7-9eb3c1f70f3c@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).