From: Zhu Yi <yi.zhu@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Eric Paris <eparis@redhat.com>,
"John W. Linville" <linville@tuxdriver.com>,
Eric Paris <eparis@parisplace.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"H. Peter Anvin" <hpa@kernel.org>,
"linux-kernel@vger.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: Tue, 01 Sep 2009 14:33:49 +0800 [thread overview]
Message-ID: <1251786829.8830.277.camel@debian> (raw)
In-Reply-To: <43e72e890908311731h626a5b9bu486653c755cda2fa@mail.gmail.com>
On Tue, 2009-09-01 at 08:31 +0800, Luis R. Rodriguez wrote:
> >>
> http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
> >>
> >> FWIW for that patch:
> >>
> >> Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> >>
> >> So -- you if you're like me and had issues with bootup lag on
> >> wireless-testing, you can probably fix your wireless-testing by
> >> pulling his patches:
> >>
> >> git pull git://git.infradead.org/users/eparis/notify.git for-linus
> >>
> >> I saw Linus had some other fixes but I'll wait for rc9 for that as
> my
> >> box seems reasonably stable right now.
> >
> > Yes, -rc8 broke pretty badly for a number of people. Linus did pull
> all
> > of the fixes that I know of. I wouldn't suggest pulling just that
> one
> > commit. All 3 of the post -rc8 patches in my tree fix -rc8
> > regressions :(
>
> Thanks, the note -- so I guess best is to just pull from Linus ontop
> of wireless-testing.
I confirm I'm also suffered with the problem on today's wireless-testing
tip (udevadm --settle hangs on boot) and the above patch does fix the
issue for me. Thanks both for identify and fix the problem.
Thanks,
-yi
next prev parent reply other threads:[~2009-09-01 6:33 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
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 [this message]
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=1251786829.8830.277.camel@debian \
--to=yi.zhu@intel.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=gregkh@suse.de \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).