From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kvm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Nicholas Piggin <npiggin@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Make virt_to_pfn() a static inline
Date: Tue, 15 Aug 2023 21:45:30 +1000 [thread overview]
Message-ID: <87il9gcyw5.fsf@mail.lhotse> (raw)
In-Reply-To: <CACRpkdZuLeMKg1vG9+8tcUtWUNN-EowhpPmt6VnGuS+f9ok81g@mail.gmail.com>
Linus Walleij <linus.walleij@linaro.org> writes:
> On Tue, Aug 15, 2023 at 9:30 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>> Linus Walleij <linus.walleij@linaro.org> writes:
>
>> > - return ((unsigned long)__va(pmd_val(pmd) & ~PMD_MASKED_BITS));
>> > + return (const void *)((unsigned long)__va(pmd_val(pmd) & ~PMD_MASKED_BITS));
>>
>> This can also just be:
>>
>> return __va(pmd_val(pmd) & ~PMD_MASKED_BITS);
>>
>> I've squashed that in.
>
> Oh you applied it, then I don't need to send revised versions, thanks Michael!
Yeah, it's in my next-test, so I can still change it if needed for a day
or two. But if you're happy with me squashing those changes in then
that's easy, no need to send a v2.
cheers
next prev parent reply other threads:[~2023-08-15 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 8:07 [PATCH] powerpc: Make virt_to_pfn() a static inline Linus Walleij
2023-08-14 12:37 ` Michael Ellerman
2023-08-14 14:29 ` Christophe Leroy
2023-08-15 7:21 ` Michael Ellerman
2023-08-14 18:22 ` Linus Walleij
2023-08-15 7:30 ` Michael Ellerman
2023-08-15 7:42 ` Linus Walleij
2023-08-15 11:45 ` Michael Ellerman [this message]
2023-08-23 11:55 ` Michael Ellerman
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=87il9gcyw5.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=kvm@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).