public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Waitz <tali-4e/A4rHm86X2JYTphGNI2Q@public.gmane.org>
To: Li Shaohua <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ACPI-DEV
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Zwane Mwaikambo <zwane-T6AQWPvKiI1fDP7aoN8Z5Q@public.gmane.org>,
	Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Subject: Re: [RFC 1/6]SEP initialization rework
Date: Wed, 6 Apr 2005 21:31:26 +0200	[thread overview]
Message-ID: <20050406193126.GA4458@admingilde.org> (raw)
In-Reply-To: <1112580349.4194.331.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

hoi :)

On Mon, Apr 04, 2005 at 10:05:56AM +0800, Li Shaohua wrote:
> -	on_each_cpu(enable_sep_cpu, NULL, 1, 1);

with this on_each_cpu call gone, you should also be able to remove the
useless info pointer in enable_sep_cpu.

-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-04-06 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  2:05 [RFC 1/6]SEP initialization rework Li Shaohua
     [not found] ` <1112580349.4194.331.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-04  8:46   ` Pavel Machek
     [not found]     ` <20050404084638.GB14642-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-04-04  8:52       ` Li Shaohua
2005-04-04 19:10   ` Zwane Mwaikambo
2005-04-05  1:00     ` Li Shaohua
     [not found]       ` <1112662825.17861.4.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-04-05  8:00         ` Zwane Mwaikambo
2005-04-06 19:31   ` Martin Waitz [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=20050406193126.GA4458@admingilde.org \
    --to=tali-4e/a4rhm86x2jytphgni2q@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pavel-AlSwsSmVLrQ@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=zwane-T6AQWPvKiI1fDP7aoN8Z5Q@public.gmane.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