[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <e152b574-a064-4f5b-9f96-ee0188ba440a@app.fastmail.com>
Date: Fri, 25 Jul 2025 18:55:54 +0200
From: "Sven Peter" <sven@...nel.org>
To: "Arnd Bergmann" <arnd@...db.de>, "Lee Jones" <lee@...nel.org>,
"Stephen Rothwell" <sfr@...b.auug.org.au>
Cc: ARM <linux-arm-kernel@...ts.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
linux-next <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the mfd tree
On Fri, Jul 25, 2025, at 13:48, Arnd Bergmann wrote:
> On Fri, Jul 25, 2025, at 13:35, Lee Jones wrote:
>> On Fri, 25 Jul 2025, Stephen Rothwell wrote:
>>
>>> The following commit is also in the arm-soc tree as a different commit
>>> (but the same patch):
>>>
>>> ba9ae011e837 ("soc: apple: rtkit: Make shmem_destroy optional")
>>>
>>> This is commit
>>>
>>> 0445eee835d6 ("soc: apple: rtkit: Make shmem_destroy optional")
>>
>> Odd. I don't see an applied email for this.
I mentioned I was going to apply it in
https://lore.kernel.org/asahi/a67fcfc9-e708-47db-8605-e20a8b54b0d1@kernel.org/
and also sent out
https://lore.kernel.org/asahi/175292958117.11653.12996215497191655678.b4-ty@kernel.org/
via b4 ty a few days ago. You should've been CCed, no idea why the
email didn't reach your inbox :(
>>
>> This was applied to MFD and a pull-request was provided for the other
>> subsystems:
>>
>> https://lore.kernel.org/all/20250724102529.GA11056@google.com/
>
> This is the one I pulled in
>
> https://lore.kernel.org/all/20250722163258.62424-1-sven@kernel.org/
>
> I did not see anything from Sven about a shared commit. I can
> throw it out again without too much trouble if you already have
> the contents. The only other commit in that branch is
> 65293c3276de ("soc: apple: Drop default ARCH_APPLE in Kconfig"),
> which I'm sure can wait as it only changes the default.
Yeah, feel free to just drop that entire PR.
I'll just include that commit in the ones I'll send next cycle.
Sven
Powered by blists - more mailing lists