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 12:58:47 +0100 [thread overview]
Message-ID: <20210504115847.b3t6zbgxxd5gntct@bigthink> (raw)
In-Reply-To: <20210504115433.nz3q4fbr62hecnmj@pengutronix.de>
On Tue, May 04, 2021 at 01:54:33PM +0200, Marc Kleine-Budde wrote:
> What's the base commit for this series?
>
> regards,
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Embedded Linux | https://www.pengutronix.de |
> Vertretung West/Dortmund | Phone: +49-231-2826-924 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Effective base is:
644022b1de9e - can: m_can: m_can_receive_skb(): add missing error handling to can_rx_offload_queue_sorted() call
(This series rebases onto can-next/testing without conflicts)
--
Regards,
Torin Cooper-Bennun
Software Engineer | maxiluxsystems.com
next prev parent reply other threads:[~2021-05-04 11:58 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 [this message]
2021-05-04 12:20 ` Marc Kleine-Budde
2021-05-04 12:48 ` Torin Cooper-Bennun
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=20210504115847.b3t6zbgxxd5gntct@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