From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, kernel@pengutronix.de, linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2018-01-26,pull-request: can-next 2018-01-26
Date: Fri, 26 Jan 2018 10:54:39 -0500 (EST) [thread overview]
Message-ID: <20180126.105439.1558417756195779166.davem@davemloft.net> (raw)
In-Reply-To: <f76dc058-dcbb-fdd7-1ad1-b46871c1ec0d@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Fri, 26 Jan 2018 11:01:41 +0100
> this is a pull request for net-next/master consisting of 3 patches.
>
> The first two patches target the CAN documentation. The first is by me
> and fixes pointer to location of fsl,mpc5200-mscan node in the mpc5200
> documentation. The second patch is by Robert Schwebel and it converts
> the plain ASCII documentation to restructured text.
>
> The third patch is by Fabrizio Castro add the r8a774[35] support to the
> rcar_can dt-bindings documentation.
Pulled, thanks Marc.
prev parent reply other threads:[~2018-01-26 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 10:01 pull-request: can-next 2018-01-26 Marc Kleine-Budde
2018-01-26 15:54 ` David Miller [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=20180126.105439.1558417756195779166.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).