From: "Stefan Mätje" <Stefan.Maetje@esd.eu>
To: mkl@pengutronix.de
Cc: o.rempel@pengutronix.de, linux-can@vger.kernel.org
Subject: [PATCH 1/1] can: j1939: j1939_session_tx_dat(): Fix build failure introduced by renaming skcb to se_skcb
Date: Fri, 16 Jul 2021 14:34:37 +0200 [thread overview]
Message-ID: <20210716123437.20825-2-Stefan.Maetje@esd.eu> (raw)
In-Reply-To: <20210716123437.20825-1-Stefan.Maetje@esd.eu>
The patch a2ea50608a02ac48371a9fab0167c1b44457913e renamed the
session skb control buffer from skcb to se_skcb. But that patch
missed one occurrence of skcb which leads to a build failure.
This patch renames also the last occurrence of skcb to fix it.
Signed-off-by: Stefan Mätje <Stefan.Maetje@esd.eu>
---
net/can/j1939/transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/can/j1939/transport.c b/net/can/j1939/transport.c
index 6c1d489c8ce2..efdf79de3db6 100644
--- a/net/can/j1939/transport.c
+++ b/net/can/j1939/transport.c
@@ -808,7 +808,7 @@ static int j1939_session_tx_dat(struct j1939_session *session)
if (offset + len > se_skb->len) {
netdev_err_once(priv->ndev,
"%s: 0x%p: requested data outside of queued buffer: offset %i, len %i, pkt.tx: %i\n",
- __func__, session, skcb->offset,
+ __func__, session, se_skcb->offset,
se_skb->len , session->pkt.tx);
ret = -EOVERFLOW;
goto out_free;
--
2.25.1
next prev parent reply other threads:[~2021-07-16 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 12:34 [PATCH 0/1] Propose patch to fix build failure on net/can/j1919/transport.c Stefan Mätje
2021-07-16 12:34 ` Stefan Mätje [this message]
2021-07-16 12:36 ` [PATCH 1/1] can: j1939: j1939_session_tx_dat(): Fix build failure introduced by renaming skcb to se_skcb Marc Kleine-Budde
2021-07-16 12:45 ` Stefan Mätje
2021-07-24 21:27 ` 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=20210716123437.20825-2-Stefan.Maetje@esd.eu \
--to=stefan.maetje@esd.eu \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.