All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, ak@suse.de,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: Fix DMI out of memory problems
Date: Wed, 19 Dec 2007 18:56:04 +0100	[thread overview]
Message-ID: <20071219175604.GA7029@elte.hu> (raw)
In-Reply-To: <82e4877d0712190909y6b449e0cgee3ba7363cd5e85b@mail.gmail.com>


* Parag Warudkar <parag.warudkar@gmail.com> wrote:

> On Dec 19, 2007 12:06 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Parag Warudkar <parag.warudkar@gmail.com> wrote:
> >
> > > Here is the right one -
> > > 2.6.24-rc5  is without patch, 2.6.24-rc5-new is with patch.
> >
> > >  DMI present.
> > > -dmi_save_oem_strings_devices: out of memory.
> > > -dmi_string: out of memory.
> >
> > ok. I guess absent a real regression/bug reported by someone who gets
> > these messages, we can do your patches in 2.6.25. DMI stuff is quite
> > hardware dependent so it's hard to get the code tested well.
> >
> 
> Yep, I agree.
> 
> Andrew if you want to keep it in -mm till 2.6.25 - that'd hopefully 
> give it some testing.

i've added it to x86.git - that gets included in -mm.

	Ingo

  reply	other threads:[~2007-12-19 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19  0:33 [PATCH] x86: Fix DMI out of memory problems Parag Warudkar
2007-12-19 10:48 ` Ingo Molnar
2007-12-19 16:48   ` Parag Warudkar
2007-12-19 16:54     ` Ingo Molnar
2007-12-19 17:00       ` Parag Warudkar
2007-12-19 17:06         ` Ingo Molnar
2007-12-19 17:09           ` Parag Warudkar
2007-12-19 17:56             ` Ingo Molnar [this message]
2007-12-21 13:41 ` Andi Kleen
2007-12-21 16:31   ` Parag Warudkar

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=20071219175604.GA7029@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parag.warudkar@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.