From: Sudeep Holla <sudeep.holla@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-efi <linux-efi@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH] ARM: efi: Simplify arch_efi_call_virt() macro by using typeof()
Date: Wed, 29 Jun 2022 10:02:30 +0100 [thread overview]
Message-ID: <20220629090230.flwocqj7na4qvwoi@bogus> (raw)
In-Reply-To: <CAMj1kXFc7CaTV3vhJrskL+VZS2rAdb320Be1mhwX4VW=pSsdJA@mail.gmail.com>
On Wed, Jun 29, 2022 at 10:58:29AM +0200, Ard Biesheuvel wrote:
> On Wed, 29 Jun 2022 at 10:57, Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > On Tue, Jun 28, 2022 at 07:58:38PM +0200, Ard Biesheuvel wrote:
> > > On Tue, 28 Jun 2022 at 16:09, Sudeep Holla <sudeep.holla@arm.com> wrote:
> > > >
> > > > On Tue, Jun 28, 2022 at 03:57:38PM +0200, Ard Biesheuvel wrote:
> > > > > On Tue, 28 Jun 2022 at 15:47, Sudeep Holla <sudeep.holla@arm.com> wrote:
> > > > > >
> > > ...
> > >
> > > > > > I am yet to figure out how asm/efi.h and linux/efi.h are included so that
> > > > > > we can have generic definition in linux/efi.h and x86 can undefine that
> > > > > > and redefine its own version.
> > > > > >
> > > > > > Does that make sense ?
> > > > > >
> > > > >
> > > > > I appreciate the effort, but for now, let's just fix the ones we need
> > > > > to fix (and the ARM one too while we're at it). PRM can only be
> > > > > enabled on x86 and arm64 anyway.
> > > >
> > > > True. OK then I will just update ARM version and leave loongarch as is.
> > > >
> > >
> > > Actually, this was rather straight-forward so I folded this change
> > > into your ARM patch.
> >
> > I see you have the generic version for all archs except arm64 and x86 as
> > we discussed earlier. Since you have even included the arm64 changes, the
> > PRMT enablement patches need to routed via your tree now as it depends on
> > the change you have in your -next.
> >
> > Are you OK with that if Rafael agrees ? I can ask him on the other thread.
> > No further changes are needed. Let me know.
> >
>
> Yes, that is fine. Or I can put that patch on a stable branch by itself.
Thanks I will check with Rafael now.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-06-29 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:59 [PATCH] ARM: efi: Simplify arch_efi_call_virt() macro by using typeof() Sudeep Holla
2022-06-28 13:16 ` Ard Biesheuvel
2022-06-28 13:47 ` Sudeep Holla
2022-06-28 13:57 ` Ard Biesheuvel
2022-06-28 14:09 ` Sudeep Holla
2022-06-28 17:58 ` Ard Biesheuvel
2022-06-29 8:56 ` Sudeep Holla
2022-06-29 8:58 ` Ard Biesheuvel
2022-06-29 9:02 ` Sudeep Holla [this message]
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=20220629090230.flwocqj7na4qvwoi@bogus \
--to=sudeep.holla@arm.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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