linux-wireless.vger.kernel.org archive mirror
 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: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43e72e890908272225w79ec5bf6kc7ef1160e5a088ae@mail.gmail.com>
     [not found] ` <tnxtyzr7vcl.fsf@pc1117.cambridge.arm.com>
     [not found]   ` <43e72e890908280952j410293fbm47b4b9d566e26c14@mail.gmail.com>
     [not found]     ` <43e72e890908281450k78cc1a2fmd4fd033ae0f4176f@mail.gmail.com>
     [not found]       ` <43e72e890908281509o44930348w581b865107ea3e98@mail.gmail.com>
2009-08-31  8:23         ` memleaks, acpi + ext4 + tty 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

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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).