mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Hughes <hughsient@gmail.com>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: Anisse Astier <anisse@astier.eu>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Johan Hovold <johan+linaro@kernel.org>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Jeremy Kerr <jk@ozlabs.org>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Anisse Astier <an.astier@criteo.com>
Subject: Re: [PATCH] efivarfs: expose used and total size
Date: Tue, 2 May 2023 12:01:57 +0100	[thread overview]
Message-ID: <CAD2FfiELuWnOCMv8hwHOQase78PpRew7HHW3ATLHrxRxFOj2fw@mail.gmail.com> (raw)
In-Reply-To: <MN0PR12MB6101768A09C5C2C78C2B9B58E2659@MN0PR12MB6101.namprd12.prod.outlook.com>

On Wed, 26 Apr 2023 at 22:50, Limonciello, Mario
<Mario.Limonciello@amd.com> wrote:
> This can be quite useful for fwupd to be capturing as well with some of the
> weird issues that look like they're probably related to how much variable
> space is left.

Yes, agreed, this will be very useful indeed. Thanks!

Richard

  reply	other threads:[~2023-05-02 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 19:58 Anisse Astier
2023-04-26 21:50 ` Limonciello, Mario
2023-05-02 11:01   ` Richard Hughes [this message]
2023-05-10 15:13 ` Ard Biesheuvel
2023-05-11 13:21   ` Anisse Astier
2023-05-15  8:59   ` Christian Brauner
2023-05-15 14:08     ` Anisse Astier

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=CAD2FfiELuWnOCMv8hwHOQase78PpRew7HHW3ATLHrxRxFOj2fw@mail.gmail.com \
    --to=hughsient@gmail.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=an.astier@criteo.com \
    --cc=andy@infradead.org \
    --cc=anisse@astier.eu \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jk@ozlabs.org \
    --cc=johan+linaro@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®