linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
	Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Marin Jerabek <martin.jerabek01@gmail.com>,
	Ondrej Ille <ondrej.ille@gmail.com>,
	Jiri Novak <jnovak@fel.cvut.cz>,
	Jaroslav Beran <jara.beran@gmail.com>,
	Petr Porazil <porazil@pikron.com>, Pavel Machek <pavel@ucw.cz>,
	Carsten Emde <c.emde@osadl.org>,
	Drew Fustini <pdp7pdp7@gmail.com>,
	Matej Vasilevski <matej.vasilevski@gmail.com>,
	Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: [PATCH v1 0/4] can: ctucanfd: clenup acoording to the actual rules and documentation linking
Date: Sun, 24 Apr 2022 18:28:07 +0200	[thread overview]
Message-ID: <cover.1650816929.git.pisa@cmp.felk.cvut.cz> (raw)

The minor problems reported by actual checkpatch.pl and patchwork
rules has been resolved at price of disable of some debugging
options used initially to locate FPGA PCIe integration problems.

The CTU CAN FD IP core driver documentation has been linked
into CAN drivers index.

The code has been tested on QEMU with CTU CAN FD IP core
included functional model of PCIe integration.

The Linux net-next CTU CAN FD driver has been tested on real Xilinx
Zynq hardware by Matej Vasilevski even together with his
timestamp support patches. Preparation for public discussion
and mainlining is work in progress.

Jiapeng Chong (2):
  can: ctucanfd: Remove unnecessary print function dev_err()
  can: ctucanfd: Remove unused including <linux/version.h>

Pavel Pisa (2):
  can: ctucanfd: remove PCI module debug parameters and core debug
    statements.
  docs: networking: device drivers: can: add ctucanfd and its author
    e-mail update

 .../can/ctu/ctucanfd-driver.rst               |  2 +-
 .../networking/device_drivers/can/index.rst   |  1 +
 drivers/net/can/ctucanfd/ctucanfd_base.c      | 34 ++-----------------
 drivers/net/can/ctucanfd/ctucanfd_pci.c       | 22 ++++--------
 drivers/net/can/ctucanfd/ctucanfd_platform.c  |  1 -
 5 files changed, 11 insertions(+), 49 deletions(-)

-- 
2.20.1



             reply	other threads:[~2022-04-24 16:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 16:28 Pavel Pisa [this message]
2022-04-24 16:28 ` [PATCH v1 1/4] can: ctucanfd: remove PCI module debug parameters and core debug statements Pavel Pisa
2022-04-25  7:48   ` Vincent Mailhol
2022-04-25  8:10     ` Pavel Pisa
2022-04-25  8:34       ` Vincent Mailhol
2022-04-24 16:28 ` [PATCH v1 2/4] can: ctucanfd: Remove unnecessary print function dev_err() Pavel Pisa
2022-04-24 16:28 ` [PATCH v1 3/4] can: ctucanfd: Remove unused including <linux/version.h> Pavel Pisa
2022-04-24 16:28 ` [PATCH v1 4/4] docs: networking: device drivers: can: add ctucanfd and its author e-mail update Pavel Pisa
2022-04-28  7:22 ` [PATCH v1 0/4] can: ctucanfd: clenup acoording to the actual rules and documentation linking Marc Kleine-Budde
2022-04-29 21:31   ` Pavel Pisa
2022-05-02  7:21     ` Marc Kleine-Budde
2022-05-02  7:35       ` Marc Kleine-Budde
     [not found]       ` <CAHQrW0_bxDyTf7pNHgXwcO=-0YRWtsxscOSWWU4fDmNYo8d-9Q@mail.gmail.com>
2022-05-03  6:46         ` Marc Kleine-Budde
2022-05-03  7:21           ` Andrew Dennison
2022-05-03  7:27           ` Pavel Pisa
2022-05-03  8:55             ` Marc Kleine-Budde
     [not found]               ` <CAA7ZjpbzaSiX6jbV5B88_VqqJga=9y0Kf_Z77Q4DN-5YfQFy0g@mail.gmail.com>
2022-05-08  2:51                 ` Andrew Dennison

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=cover.1650816929.git.pisa@cmp.felk.cvut.cz \
    --to=pisa@cmp.felk.cvut.cz \
    --cc=c.emde@osadl.org \
    --cc=davem@davemloft.net \
    --cc=jara.beran@gmail.com \
    --cc=jnovak@fel.cvut.cz \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.jerabek01@gmail.com \
    --cc=matej.vasilevski@gmail.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=ondrej.ille@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=pdp7pdp7@gmail.com \
    --cc=porazil@pikron.com \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.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).