From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de
Subject: [PATCH net-next 0/2] pull-request: can-next 2023-02-08
Date: Wed, 8 Feb 2023 22:00:12 +0100 [thread overview]
Message-ID: <20230208210014.3169347-1-mkl@pengutronix.de> (raw)
Hello netdev-team,
this is a pull request of 2 patches for net-next/master.
The 1st patch is by Oliver Hartkopp and cleans up the CAN_RAW's
raw_setsockopt() for CAN_RAW_FD_FRAMES.
The 2nd patch is by me and fixes the compilation if
CONFIG_CAN_CALC_BITTIMING is disabled. (Problem introduced in last
pull request to next-next.)
regards,
Marc
---
The following changes since commit e6ebe6c12355538e9238e2051bd6757b12dbfe9c:
Merge branch 'taprio-auto-qmaxsdu-new-tx' (2023-02-08 09:48:53 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-6.3-20230208
for you to fetch changes up to 65db3d8b5231bd430c12150258125aca155aea97:
can: bittiming: can_calc_bittiming(): add missing parameter to no-op function (2023-02-08 21:53:24 +0100)
----------------------------------------------------------------
linux-can-next-for-6.3-20230208
----------------------------------------------------------------
Marc Kleine-Budde (1):
can: bittiming: can_calc_bittiming(): add missing parameter to no-op function
Oliver Hartkopp (1):
can: raw: use temp variable instead of rolling back config
include/linux/can/bittiming.h | 2 +-
net/can/raw.c | 11 ++++++-----
2 files changed, 7 insertions(+), 6 deletions(-)
next reply other threads:[~2023-02-08 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 21:00 Marc Kleine-Budde [this message]
2023-02-08 21:00 ` [PATCH net-next 1/2] can: raw: use temp variable instead of rolling back config Marc Kleine-Budde
2023-02-09 5:40 ` patchwork-bot+netdevbpf
2023-02-08 21:00 ` [PATCH net-next 2/2] can: bittiming: can_calc_bittiming(): add missing parameter to no-op function 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=20230208210014.3169347-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--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).