mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Antonino Daplas <adaplas@gmail.com>, Olaf Hering <olaf@aepfle.de>,
	Ville Syrj?l? <syrjala@sci.fi>,
	Christoph Lameter <clameter@sgi.com>,
	Dave Airlie <airlied@linux.ie>,
	Andrea Righi <righiandr@users.sourceforge.net>,
	Netdev <netdev@vger.kernel.org>,
	linux-wireless@vger.kernel.org, Samuel Ortiz <samuel@sortiz.org>,
	Andrey Borzenkov <arvidjaar@mail.ru>,
	Samuel Ortiz <samuel@sortiz.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Chad Tindel <ctindel@users.sourceforge.net>,
	Olaf Hering <olaf@aepfle.de>
Subject: Re: [2/2] 2.6.22-rc6: known regressions with patches
Date: Mon, 25 Jun 2007 11:27:32 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0706251126040.3593@woody.linux-foundation.org> (raw)
In-Reply-To: <467F8F63.2070101@googlemail.com>



On Mon, 25 Jun 2007, Michal Piotrowski wrote:
> 
> Memory management
> 
> Subject    : bug in i386 MTRR initialization
> References : http://lkml.org/lkml/2007/5/19/93
> Submitter  : Andrea Righi <righiandr@users.sourceforge.net>
> Status     : patch available

This one wasn't a bug in the first place, it was just the regular warning 
for kmalloc-size-0. The "BUG" string was confusing and has been fixed, and 
the warning for size-0 has gone away and been replaced by returning a 
pointer that will fault on dereference instead.

So please remove this one.

		Linus

      reply	other threads:[~2007-06-25 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <467F894C.4000604@googlemail.com>
2007-06-25  9:48 ` Michal Piotrowski
2007-06-25 18:27   ` Linus Torvalds [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=alpine.LFD.0.98.0706251126040.3593@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=adaplas@gmail.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=arvidjaar@mail.ru \
    --cc=bjorn.helgaas@hp.com \
    --cc=clameter@sgi.com \
    --cc=ctindel@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=righiandr@users.sourceforge.net \
    --cc=samuel@sortiz.org \
    --cc=syrjala@sci.fi \
    /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®