All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	"H. Peter Anvin" <hpa@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: memleaks, acpi + ext4 + tty
Date: Mon, 31 Aug 2009 15:47:53 -0400	[thread overview]
Message-ID: <20090831194753.GH5631@tuxdriver.com> (raw)
In-Reply-To: <43e72e890908311243u50b9323fveda9feaaa4d8efdb@mail.gmail.com>

On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 31, 2009 at 12:33 PM, John W.
> Linville<linville@tuxdriver.com> wrote:

> > My guess is that the culprit is between
> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
> 
> But the issue is *not* in linux-2.6-allstable, it is only present on
> wireless-testing, and I went as far back as merge-2009-08-28. I was
> using whatever tag was available prior to you moving to rc8, and that
> worked.

OK, then I can only guess that something went wrong in your bisection
(e.g. dirty build, something not marked properly, etc).  That, or
different .config files between your linux-2.6-allstable build and
the merge-2009-08-28 build of wireless-testing?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-08-31 20:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  5:25 memleaks, acpi + ext4 + tty Luis R. Rodriguez
2009-08-28 16:32 ` Catalin Marinas
2009-08-28 16:52   ` Luis R. Rodriguez
2009-08-28 21:50     ` Luis R. Rodriguez
2009-08-28 22:09       ` Luis R. Rodriguez
2009-08-31  8:23         ` Luis R. Rodriguez
2009-08-31 17:50           ` Luis R. Rodriguez
2009-08-31 18:37             ` Luis R. Rodriguez
2009-08-31 19:30               ` Luis R. Rodriguez
2009-08-31 19:33                 ` John W. Linville
2009-08-31 19:43                   ` Luis R. Rodriguez
2009-08-31 19:47                     ` John W. Linville [this message]
2009-08-31 20:02                       ` Luis R. Rodriguez
2009-08-31 23:54                         ` Luis R. Rodriguez
2009-09-01  0:26                           ` Eric Paris
2009-09-01  0:31                             ` Luis R. Rodriguez
2009-09-01  6:33                               ` Zhu Yi
2009-09-01 18:00                                 ` Luis R. Rodriguez
2009-08-31 19:58                     ` Luis R. Rodriguez
2009-09-01 22:10                       ` H. Peter Anvin
2009-08-29 21:41     ` Catalin Marinas
2009-08-30 16:34   ` Aneesh Kumar K.V
2009-08-30 17:17     ` Theodore Tso
2009-08-30 17:29       ` Luis R. Rodriguez
2009-08-30 18:24         ` Theodore Tso
2009-09-01 17:59           ` Luis R. Rodriguez

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=20090831194753.GH5631@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@suse.de \
    --cc=hpa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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 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.