public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Matt Tolentino <metolent@snoqualmie.dp.intel.com>
Cc: davidm@napali.hpl.hp.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org, matthew.e.tolentino@intel.com
Subject: Re: [patch] efivars update for 2.6.1
Date: Wed, 14 Jan 2004 03:10:15 +0000	[thread overview]
Message-ID: <20040113191015.20415de3.akpm@osdl.org> (raw)
In-Reply-To: <200401131824.i0DIOMcA031105@snoqualmie.dp.intel.com>

Matt Tolentino <metolent@snoqualmie.dp.intel.com> wrote:
>
> Andrew, David:
> 
> Here's a patch that has been posted here before, but not yet
> merged.

Big, isn't it?

> Essentially, it converts efivars (i.e. Matt Domsch's 
> driver that provides access to the EFI variable runtime 
> services) to export variable information and systab info via 
> sysfs.

I'd need confirmation from David M-T and if poss a quick review from Greg K-H.

From a super-quick scan:

- Someone seems to have mangled the files with an editor which doesn't
  understand hard tabs.

- This function:

	> +static void __exit
	> +efivars_exit(void)
	> +{
	> +	struct list_head *pos, *n;
	> +
	> +        spin_lock(&efivars_lock);
	> +
	> +	list_for_each_safe(pos, n, &efivar_list)
	> +		efivar_unregister(get_efivar_entry(pos));
	> +
	> +	spin_unlock(&efivars_lock);
	> +
	> +	subsystem_unregister(&vars_subsys);
	> +	firmware_unregister(&efi_subsys);
	> +}

  cannot call efivar_unregister() under spinlock - it does all sorts of
  illegal-under-spinlock things.



  reply	other threads:[~2004-01-14  3:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 17:12 [patch] efivars update for 2.6.1 Matt Tolentino
2004-01-14  3:10 ` Andrew Morton [this message]
2004-01-14 22:53   ` David Mosberger
2004-01-15  3:40 ` Matt Domsch
2004-01-15 18:28 ` Matt Tolentino
2004-01-15 20:04   ` David Mosberger
2004-01-16 20:16 ` Matt Tolentino

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=20040113191015.20415de3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=metolent@snoqualmie.dp.intel.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