public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes-sJ/iWh9BUns@public.gmane.org (Jesse Barnes)
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [BKPATCH] ACPI update for 2.6
Date: Thu, 18 Dec 2003 13:25:52 -0800	[thread overview]
Message-ID: <20031218212552.GA956@sgi.com> (raw)
In-Reply-To: <20031218211213.GA845-sJ/iWh9BUns@public.gmane.org>

willy just pointed out that these patches should probably use pr_debug()
instead.  If you're ok with the idea, I can create a new patch.

Thanks,
Jesse

On Thu, Dec 18, 2003 at 01:12:13PM -0800, Jesse Barnes wrote:
> On Thu, Dec 18, 2003 at 05:11:50AM -0500, Len Brown wrote:
> > Hi Andrew/Linus, please do a 
> > 
> > 	bk pull http://linux-acpi.bkbits.net/linux-acpi-release-2.6.0
> 
> Len, could you please include these two patches in your next update if
> you think they're ok?  They make the boot a lot quieter on big NUMA
> boxes...
> 
> Thanks,
> Jesse


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

      parent reply	other threads:[~2003-12-18 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 10:11 [BKPATCH] ACPI update for 2.6 Len Brown
     [not found] ` <1071742310.2496.217.camel-D2Zvc0uNKG8@public.gmane.org>
2003-12-18 21:12   ` Jesse Barnes
     [not found]     ` <20031218211213.GA845-sJ/iWh9BUns@public.gmane.org>
2003-12-18 21:25       ` Jesse Barnes [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=20031218212552.GA956@sgi.com \
    --to=jbarnes-sj/iwh9buns@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 \
    /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