From: Michael Ellerman <mpe@ellerman.id.au>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Michael Ellerman <patch-notifications@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/vdso: Remove unused clockmode asm offsets
Date: Tue, 19 Nov 2024 14:26:22 +1100 [thread overview]
Message-ID: <877c8zj44h.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20241118075902-8b0cf2ea-d772-4c05-9b5d-14aba194e649@linutronix.de>
Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> Hi Michael,
>
> On Sun, Nov 17, 2024 at 11:09:57PM +1100, Michael Ellerman wrote:
>> On Wed, 13 Nov 2024 09:06:58 +0100, Thomas Weißschuh wrote:
>> > These offsets are not used anymore, delete them.
>> >
>> >
>>
>> Applied to powerpc/next.
>>
>> [1/1] powerpc/vdso: Remove unused clockmode asm offsets
>> https://git.kernel.org/powerpc/c/d7a82238cb8c77d4ed8cc97cd556c5f3e64bc749
>
> Thanks!
>
> Is there any chance to get this merged as part of topic/vdso?
I could apply it there, but I don't think it will be necessary, because
topic/vdso will be empty vs mainline as soon as I send my pull request
for v6.13.
> My vdso rework patches for the 6.14 cycle rely on these removals.
Assuming you rebase that series onto v6.13-rc1 or later, this commit
will be included in that base.
But let me know if I'm misunderstanding something.
cheers
next prev parent reply other threads:[~2024-11-19 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 8:06 Thomas Weißschuh
2024-11-13 10:20 ` Christophe Leroy
2024-11-17 12:09 ` Michael Ellerman
2024-11-18 7:00 ` Thomas Weißschuh
2024-11-19 3:26 ` Michael Ellerman [this message]
2024-11-19 8:02 ` Thomas Weißschuh
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=877c8zj44h.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=patch-notifications@ellerman.id.au \
--cc=thomas.weissschuh@linutronix.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
all inboxes | Powered by JetHome®