linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Brett Werling <bwerl.dev@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH] can: tcan4x5x: fix power regulator retrieval during probe
Date: Tue, 17 Jun 2025 17:53:44 +0200	[thread overview]
Message-ID: <20250617-visionary-bouncy-galago-dbcf1c-mkl@pengutronix.de> (raw)
In-Reply-To: <3302f4d4-a863-4a88-83af-8f09b4191bb3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

Hello Brett,

On 17.06.2025 10:17:44, Brett Werling wrote:
> Do you know when the final patch will be available on
> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git? I'd like
> to reference the proper SHA1 when back-porting to my company's kernel
> repository.

I've just send a PR to the netdev team and if I don't get any objections
the patch will go mainline as:

| db2272054520 ("can: tcan4x5x: fix power regulator retrieval during probe")

The commit is now available on
https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git

regards,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde          |
Embedded Linux                   | https://www.pengutronix.de |
Vertretung Nürnberg              | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-9   |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2025-06-17 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 19:18 [PATCH] can: tcan4x5x: fix power regulator retrieval during probe Brett Werling
2025-06-13  7:30 ` Marc Kleine-Budde
     [not found]   ` <3302f4d4-a863-4a88-83af-8f09b4191bb3@gmail.com>
2025-06-17 15:53     ` Marc Kleine-Budde [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=20250617-visionary-bouncy-galago-dbcf1c-mkl@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=bwerl.dev@gmail.com \
    --cc=linux-can@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).