From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: pull-request: can 2017-04-04
Date: Tue, 4 Apr 2017 17:59:47 +0200 [thread overview]
Message-ID: <20170404155949.30965-1-mkl@pengutronix.de> (raw)
Hello David,
this is a pull request of two patches for net/master.
The first patch by Markus Marb fixes a register read access in the ifi driver.
The second patch by Geert Uytterhoeven for the rcar driver remove the printing
of a kernel virtual address.
regards,
Marc
---
The following changes since commit 0b9aefea860063bb39e36bd7fe6c7087fed0ba87:
tcp: minimize false-positives on TCP/GRO check (2017-04-03 18:43:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git
for you to fetch changes up to ca257b9e2d807ab6cb2678ecc7b74aaf4651f597:
can: rcar_can: Do not print virtual addresses (2017-04-04 17:49:59 +0200)
----------------------------------------------------------------
Geert Uytterhoeven (1):
can: rcar_can: Do not print virtual addresses
Markus Marb (1):
can: ifi: use correct register to read rx status
drivers/net/can/ifi_canfd/ifi_canfd.c | 2 +-
drivers/net/can/rcar/rcar_can.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
next reply other threads:[~2017-04-04 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 15:59 Marc Kleine-Budde [this message]
2017-04-04 15:59 ` [PATCH 1/2] can: ifi: use correct register to read rx status Marc Kleine-Budde
2017-04-04 15:59 ` [PATCH 2/2] can: rcar_can: Do not print virtual addresses Marc Kleine-Budde
2017-04-05 17:37 ` pull-request: can 2017-04-04 David Miller
2017-04-05 17:56 ` Uwe Kleine-König
2017-04-07 9:00 ` Marc Kleine-Budde
2017-04-08 16:24 ` pull-request: can 2017-04-04,Re: " 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=20170404155949.30965-1-mkl@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).