From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: pull-request: can-next 2018-01-16,pull-request: can-next 2018-01-16
Date: Wed, 17 Jan 2018 16:08:43 -0500 (EST) [thread overview]
Message-ID: <20180117.160843.201643557390707149.davem@davemloft.net> (raw)
In-Reply-To: <335207aa-3313-a981-ee39-ce5c861470c8@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Tue, 16 Jan 2018 15:28:46 +0100
> this is a pull request for net-next/master consisting of 9 patches.
>
> This is a series of patches, some of them initially by Franklin S Cooper
> Jr, which was picked up by Faiz Abbas. Faiz Abbas added some patches
> while working on this series, I contributed one as well.
>
> The first two patches add support to CAN device infrastructure to limit
> the bitrate of a CAN adapter if the used CAN-transceiver has a certain
> maximum bitrate.
>
> The remaining patches improve the m_can driver. They add support for
> bitrate limiting to the driver, clean up the driver and add support for
> runtime PM.
Pulled.
next prev parent reply other threads:[~2018-01-17 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 14:28 pull-request: can-next 2018-01-16 Marc Kleine-Budde
2018-01-17 21:08 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-19 9:48 Marc Kleine-Budde
2018-01-19 15:31 ` pull-request: can-next 2018-01-16,pull-request: " David Miller
2018-07-27 9:40 pull-request: " Marc Kleine-Budde
2018-07-29 15:35 ` pull-request: can-next 2018-01-16,pull-request: " David Miller
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=20180117.160843.201643557390707149.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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).