public inbox for linux-can@vger.kernel.org
 help / color / mirror / Atom feed
From: Torin Cooper-Bennun <torin@maxiluxsystems.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [REPOST PATCH 0/4] can: m_can: various regmask-related cleanup
Date: Tue, 4 May 2021 13:48:41 +0100	[thread overview]
Message-ID: <20210504124841.rcdy5lmls3y6hubw@bigthink> (raw)
In-Reply-To: <20210504122017.suk5coyk6nmc54y7@pengutronix.de>

On Tue, May 04, 2021 at 02:20:17PM +0200, Marc Kleine-Budde wrote:
> Hmmm...not here:
> 
> | ➜ (pts/13) frogger@hardanger:socketcan/linux (next✗) git lg -1                                                                        
> | 644022b1de9e (HEAD -> next) can: m_can: m_can_receive_skb(): add missing error handling to can_rx_offload_queue_sorted() call
> | 
> | ➜ (pts/13) frogger@hardanger:socketcan/linux (next) git am -s --reject ./20210504_torin_can_m_can_various_regmask_related_cleanup.mbx
> | Applying: can: m_can: use bits.h macros for all regmasks
> | Checking patch drivers/net/can/m_can/m_can.c...
> | error: while searching for:
> | 
> |                 net->stats.tx_errors++;
> |                 if (cdev->version > 30)
> |                         putidx = ((m_can_read(cdev, M_CAN_TXFQS) &
> |                                    TXFQS_TFQPI_MASK) >> TXFQS_TFQPI_SHIFT);
> | 
> |                 can_free_echo_skb(cdev->net, putidx);
> |                 cdev->tx_skb = NULL;
> | 

Yup, found my mistake, my tree is not consistent with can-next. Let me
submit a v2. They'll be based directly on can-next/testing.

--
Regards,

Torin Cooper-Bennun
Software Engineer | maxiluxsystems.com


      reply	other threads:[~2021-05-04 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 11:48 [REPOST PATCH 0/4] can: m_can: various regmask-related cleanup Torin Cooper-Bennun
2021-05-04 11:48 ` [PATCH 1/4] can: m_can: use bits.h macros for all regmasks Torin Cooper-Bennun
2021-05-04 11:48 ` [PATCH 2/4] can: m_can: clean up CCCR reg defs, order by revs Torin Cooper-Bennun
2021-05-04 11:49 ` [PATCH 3/4] can: m_can: make TXESC, RXESC config more explicit Torin Cooper-Bennun
2021-05-04 11:49 ` [PATCH 4/4] can: m_can: fix whitespace in a few comments Torin Cooper-Bennun
2021-05-04 11:54 ` [REPOST PATCH 0/4] can: m_can: various regmask-related cleanup Marc Kleine-Budde
2021-05-04 11:58   ` Torin Cooper-Bennun
2021-05-04 12:20     ` Marc Kleine-Budde
2021-05-04 12:48       ` Torin Cooper-Bennun [this message]

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=20210504124841.rcdy5lmls3y6hubw@bigthink \
    --to=torin@maxiluxsystems.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox