From: Krzysztof Kozlowski <krzk@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: soc@kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ~RISC-V~Microchip soc fixes for v7.0-rc6
Date: Wed, 1 Apr 2026 13:44:04 +0200 [thread overview]
Message-ID: <20260401-bold-positive-flounder-6e7b0d@quoll> (raw)
In-Reply-To: <20260326-vertebrae-relatable-adfa3baabfd6@spud>
On Thu, Mar 26, 2026 at 11:21:39AM +0000, Conor Dooley wrote:
> Hey folks,
>
> Another small PR here, worth pointing out that the exact contents has
> been in linux-next but not as these commit hashes yet, I squashed a
> fixup patch just now that I hadn't realised got pushed without being
> squashed. Might be worth letting it marinate for a few days if that's
> a concern.
>
> Cheers,
> Conor.
>
> The following changes since commit 0528a348b04b327a4611e29589beb4c9ae81304a:
>
> cache: ax45mp: Fix device node reference leak in ax45mp_cache_init() (2026-02-06 19:54:40 +0000)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/riscv-soc-fixes-for-v7.0-rc6
>
> for you to fetch changes up to c7596f9001e2b83293e3658e4e1addde69bb335d:
>
> firmware: microchip: fail auto-update probe if no flash found (2026-03-26 11:14:11 +0000)
Thanks, applied
Probably better if the fixes branch would move to v7.0-rc1, not
continuing the v6.19.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-01 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 11:21 [GIT PULL] ~RISC-V~Microchip soc fixes for v7.0-rc6 Conor Dooley
2026-04-01 11:44 ` Krzysztof Kozlowski [this message]
2026-04-01 12:13 ` Conor Dooley
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=20260401-bold-positive-flounder-6e7b0d@quoll \
--to=krzk@kernel.org \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@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