public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <Brice.Goglin-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>
To: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Brown,
	Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 2.6.15-mm2
Date: Sat, 07 Jan 2006 18:38:34 -0500	[thread overview]
Message-ID: <43C050FA.9040400@ens-lyon.org> (raw)
In-Reply-To: <20060107145800.113d7de5.akpm-3NddpPZAyC0@public.gmane.org>

Andrew Morton wrote:

>Brice Goglin <Brice.Goglin-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org> wrote:
>  
>
>>2) acpi-cpufreq does not load either, returns ENODEV too. It's probably
>> git-acpi. I tried to revert it but there are lots of other patches
>> depending on it, so I finally gave up.
>>    
>>
>
>OK, let me try to reproduce this.  acpi and cpufreq are fully merged up, so
>this bug may well be in mainline now.
>
>  
>
>> 3) wpa_supplicant does not find my WPA network anymore (while iwlist
>> scanning sees). I didn't see anything relevant in dmesg. My driver is
>> ipw2200.
>>    
>>
>
>It's things like this which make me consider a career in carpentry.
>
>I assume 2.6.15 works OK?
>  
>

2.6.15 and 2.6.15-git3 both don't show any of these issues. Did acpi and
cpufreq get merged after -git3 ?

thanks,
Brice

-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2006-01-07 23:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060107052221.61d0b600.akpm@osdl.org>
     [not found] ` <20060107052221.61d0b600.akpm-3NddpPZAyC0@public.gmane.org>
2006-01-07 18:19   ` [-mm patch] drivers/acpi/: make two functions static Adrian Bunk
     [not found] ` <43C0172E.7040607@ens-lyon.org>
     [not found]   ` <43C0172E.7040607-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>
2006-01-07 22:58     ` 2.6.15-mm2 Andrew Morton
     [not found]       ` <20060107145800.113d7de5.akpm-3NddpPZAyC0@public.gmane.org>
2006-01-07 23:38         ` Brice Goglin [this message]
     [not found]           ` <43C050FA.9040400-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>
2006-01-08 12:24             ` 2.6.15-mm2 Andrew Morton
     [not found]               ` <20060108042425.4d0b8a76.akpm-3NddpPZAyC0@public.gmane.org>
2006-01-08 14:39                 ` 2.6.15-mm2 Brice Goglin
     [not found]                   ` <43C12404.1010306-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>
2006-01-08 18:56                     ` 2.6.15-mm2 Andrew Morton
2006-01-08 10:31         ` 2.6.15-mm2 Erik Slagter
     [not found]           ` <1136716282.7377.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-01-09  5:03             ` 2.6.15-mm2 Dave Jones
2006-01-08  8:16 2.6.15-mm2 Brown, Len
2006-01-08 14:23 ` 2.6.15-mm2 Brice Goglin
  -- strict thread matches above, loose matches on Subject: below --
2006-01-08 17:58 2.6.15-mm2 Brown, Len
2006-01-08 18:18 2.6.15-mm2 Brown, Len

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=43C050FA.9040400@ens-lyon.org \
    --to=brice.goglin-vyw+cpy1g1pg9huczpvpmw@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox