From: Dario Binacchi <dario.binacchi@amarulasolutions.com>
To: linux-kernel@vger.kernel.org
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Coiby Xu <coiby.xu@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
M Chetan Kumar <m.chetan.kumar@intel.com>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org
Subject: [RFC PATCH 0/2] Add the first documentation for a CAN driver
Date: Fri, 7 Jan 2022 09:13:04 +0100 [thread overview]
Message-ID: <20220107081306.3681899-1-dario.binacchi@amarulasolutions.com> (raw)
The series was born from the need to document the enabling at runtime
reception of RTR frames for the Flexcan CAN controller.
For more details see https://lore.kernel.org/all/20220106105415.pdmrdgnx6p2tyff6@pengutronix.de/
Dario Binacchi (2):
docs: networking: device drivers: add can sub-folder
docs: networking: device drivers: can: add flexcan
.../device_drivers/can/freescale/flexcan.rst | 25 +++++++++++++++++++
.../networking/device_drivers/can/index.rst | 20 +++++++++++++++
.../networking/device_drivers/index.rst | 1 +
3 files changed, 46 insertions(+)
create mode 100644 Documentation/networking/device_drivers/can/freescale/flexcan.rst
create mode 100644 Documentation/networking/device_drivers/can/index.rst
--
2.32.0
next reply other threads:[~2022-01-07 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 8:13 Dario Binacchi [this message]
2022-01-07 8:13 ` [RFC PATCH 1/2] docs: networking: device drivers: add can sub-folder Dario Binacchi
2022-01-07 8:13 ` [RFC PATCH 2/2] docs: networking: device drivers: can: add flexcan Dario Binacchi
2022-01-07 19:20 ` [RFC PATCH 0/2] Add the first documentation for a CAN driver Marc Kleine-Budde
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=20220107081306.3681899-1-dario.binacchi@amarulasolutions.com \
--to=dario.binacchi@amarulasolutions.com \
--cc=coiby.xu@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chetan.kumar@intel.com \
--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