mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: soc@kernel.org, jonathan.cameron@huawei.com,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V soc fixes for v7.0-rc1
Date: Tue, 3 Mar 2026 09:41:51 +0000	[thread overview]
Message-ID: <20260303-crazy-shrink-ef2c085c99c4@spud> (raw)
In-Reply-To: <CAD++jLkDHh_WozDAot4c=1kYwy24sjH9-5_i8-Vmi6oXLp9wUw@mail.gmail.com>

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

On Tue, Mar 03, 2026 at 09:15:14AM +0100, Linus Walleij wrote:
> Hi Conor,
> 
> On Fri, Feb 13, 2026 at 1:20 PM Conor Dooley <conor@kernel.org> wrote:
> 
> > Conor Dooley (1):
> >       riscv: dts: microchip: add can resets to mpfs
> >
> > Felix Gu (2):
> >       cache: starfive: fix device node leak in starlink_cache_init()
> >       cache: ax45mp: Fix device node reference leak in ax45mp_cache_init()
> >
> > Zilin Guan (1):
> >       soc: microchip: mpfs: Fix memory leak in mpfs_sys_controller_probe()
> 
> You have DTS fixes mixed up with cache/SoC fixes, this is
> a bit unorthodox, is there some hard dependency or can you send
> the DTS fix separately?

There's no dependency of course, I'll split it out.
Ordinarily I would always split them, but I'd swear I was told at one
point that since fixes were on one branch in the soc tree that it was
okay for me to do the same. In this case I did it on one branch to be
less work to get onto a potential fixes PR that went out before -rc1.

> 
> I guess we could also split it off manually ... I'm just a bit insecure
> with that.
> 
> Yours,
> Linus Walleij

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

  reply	other threads:[~2026-03-03  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 12:20 Conor Dooley
2026-03-03  8:15 ` Linus Walleij
2026-03-03  9:41   ` Conor Dooley [this message]
2026-03-03  9:51     ` Linus Walleij
2026-03-05 13:26       ` Arnd Bergmann

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=20260303-crazy-shrink-ef2c085c99c4@spud \
    --to=conor@kernel.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=linusw@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

all inboxes | Powered by JetHome®