linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Hedi Berriche <hedi.berriche@hpe.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-efi@vger.kernel.org,
	linux-kernel@vger.kernel.org, Russ Anderson <rja@hpe.com>,
	Mike Travis <mike.travis@hpe.com>,
	Dimitri Sivanich <sivanich@hpe.com>,
	Steve Wahl <steve.wahl@hpe.com>
Subject: Re: [PATCH 1/3] efi/x86: turn EFI runtime semaphore into a global lock
Date: Tue, 15 Jan 2019 19:55:10 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1901151953370.1655@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190109104541.25733-2-hedi.berriche@hpe.com>

On Wed, 9 Jan 2019, Hedi Berriche wrote:

> Make efi_runtime_lock semaphore global so that it can be used by EFI
> runtime callers that may be defined outside efi/runtime-wrappers.c.

The changelog should mention why the lock is renamed. I have no strong
opinion, but to apply that I need an Ack from Ard.

Thanks,

	tglx

  reply	other threads:[~2019-01-15 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 10:45 [PATCH 0/3] Protect against concurrent calls into UV BIOS Hedi Berriche
2019-01-09 10:45 ` [PATCH 1/3] efi/x86: turn EFI runtime semaphore into a global lock Hedi Berriche
2019-01-15 18:55   ` Thomas Gleixner [this message]
2019-01-15 19:35     ` Hedi Berriche
2019-01-26 14:03   ` Ard Biesheuvel
2019-01-09 10:45 ` [PATCH 2/3] x86/platform/UV: kill uv_bios_call_reentrant() as it has no callers Hedi Berriche
2019-01-26 14:04   ` Ard Biesheuvel
2019-01-09 10:45 ` [PATCH 3/3] x86/platform/UV: use efi_runtime_sem to serialise BIOS calls Hedi Berriche
2019-01-10  7:13   ` Bhupesh Sharma
2019-01-14 11:30     ` Hedi Berriche
2019-01-26 14:10   ` Ard Biesheuvel

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=alpine.DEB.2.21.1901151953370.1655@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bp@alien8.de \
    --cc=hedi.berriche@hpe.com \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=mingo@redhat.com \
    --cc=rja@hpe.com \
    --cc=sivanich@hpe.com \
    --cc=steve.wahl@hpe.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).