From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Michal Jaegermann <michal@harddata.com>,
Dave Jones <davej@codemonkey.org.uk>,
arjan@infradead.org, len.brown@intel.com, davem@davemloft.net,
torvalds@osdl.org, linux-kernel@vger.kernel.org, axboe@suse.de,
James.Bottomley@steeleye.com, greg@kroah.com,
linux-acpi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, luming.yu@intel.com,
lk@bencastricum.nl, sanjoy@mrao.cam.ac.uk,
helgehaf@aitel.hist.no, fluido@fluido.as, gbruchhaeuser@gmx.de,
Nicolas.Mailhot@LaPoste.net, perex@suse.cz, tiwai@suse.de,
patrizio.bassi@gmail.com, bni.swe@gmail.com, arvidjaar@mail.ru,
p_christ@hol.gr, ghrt@dial.kappa.ro, jinhong.hu@gmail.com,
andrew.vasquez@qlogic.com, linux-scsi@vger.kernel.org,
bcrl@kvack.org
Subject: Re: Linux 2.6.16-rc3
Date: Fri, 17 Feb 2006 00:04:18 +0100 [thread overview]
Message-ID: <20060216230418.GN3490@openzaurus.ucw.cz> (raw)
In-Reply-To: <20060213192838.64013c6c.akpm@osdl.org>
Hi!
> That's suspend-to-disk, yes?
>
> Dave, would you have the 2.6.15-1.1830_FC4 -> 2.6.15-1.1831_FC4 details
> handy? There surely can't be much difference?
>
> There seem to be several ACPI problems there. Do we have a reliable means
> of feeding such reports up into the (for example) acpi developers?
>
> <I have this vaguely unsettled feeling that distros must get more bug
> reports than the usptream developers, yet we hear so little about it>
Its about 1:1 upstream:suse bugs for me... Unfortunately
suse bugs are often for old kernel...
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2006-02-16 23:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 8:02 Linux 2.6.16-rc3 Brown, Len
2006-02-13 8:12 ` Andrew Morton
2006-02-13 8:42 ` Sanjoy Mahajan
2006-02-13 8:57 ` Arjan van de Ven
2006-02-14 3:08 ` Michal Jaegermann
2006-02-14 3:28 ` Andrew Morton
2006-02-14 4:48 ` Dave Jones
2006-02-14 5:29 ` Arjan van de Ven
2006-02-14 6:22 ` Michal Jaegermann
2006-02-16 23:04 ` Pavel Machek [this message]
2006-02-14 3:30 ` Lee Revell
2006-02-14 6:55 ` Michal Jaegermann
2006-02-14 5:31 ` Arjan van de Ven
2006-02-14 21:17 ` Sanjoy Mahajan
-- strict thread matches above, loose matches on Subject: below --
2006-02-14 6:23 Brown, Len
2006-02-13 7:07 Brown, Len
2006-02-13 7:13 ` David S. Miller
2006-02-13 7:43 ` Sanjoy Mahajan
2006-02-13 6:59 Brown, Len
[not found] <Pine.LNX.4.64.0602121709240.3691@g5.osdl.org>
2006-02-13 3:05 ` Andrew Morton
2006-02-13 3:22 ` Trond Myklebust
2006-02-13 3:28 ` Sanjoy Mahajan
2006-02-13 3:36 ` Jeff Garzik
2006-02-13 4:40 ` James Bottomley
2006-02-13 7:04 ` Arjan van de Ven
2006-02-13 8:11 ` Jens Axboe
2006-02-13 9:22 ` Patrizio Bassi
2006-02-13 12:02 ` Takashi Iwai
2006-02-13 12:37 ` Patrizio Bassi
2006-02-13 13:13 ` Takashi Iwai
2006-02-13 13:31 ` Patrizio Bassi
2006-02-13 14:15 ` Takashi Iwai
2006-02-13 14:34 ` Patrizio Bassi
2006-02-13 14:39 ` Takashi Iwai
2006-02-13 13:09 ` Rafael J. Wysocki
2006-02-13 13:51 ` Takashi Iwai
2006-02-13 19:33 ` Rafael J. Wysocki
2006-02-13 20:38 ` Greg KH
2006-02-14 16:34 ` James Bottomley
2006-02-16 1:56 ` James Bottomley
2006-02-16 17:12 ` Russell King
2006-02-16 17:34 ` Stefan Richter
2006-02-16 17:57 ` James Bottomley
2006-02-16 18:09 ` Russell King
2006-02-16 18:14 ` James Bottomley
2006-02-16 18:18 ` Russell King
2006-02-16 19:09 ` James Bottomley
2006-02-16 20:01 ` Jens Axboe
2006-02-18 0:42 ` James Bottomley
2006-02-18 1:00 ` Greg KH
2006-02-18 2:12 ` Roland Dreier
2006-02-18 5:30 ` Matthew Wilcox
2006-02-18 21:06 ` Helge Hafting
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=20060216230418.GN3490@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=James.Bottomley@steeleye.com \
--cc=Nicolas.Mailhot@LaPoste.net \
--cc=akpm@osdl.org \
--cc=andrew.vasquez@qlogic.com \
--cc=arjan@infradead.org \
--cc=arvidjaar@mail.ru \
--cc=axboe@suse.de \
--cc=bcrl@kvack.org \
--cc=bni.swe@gmail.com \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=fluido@fluido.as \
--cc=gbruchhaeuser@gmx.de \
--cc=ghrt@dial.kappa.ro \
--cc=greg@kroah.com \
--cc=helgehaf@aitel.hist.no \
--cc=jinhong.hu@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=lk@bencastricum.nl \
--cc=luming.yu@intel.com \
--cc=michal@harddata.com \
--cc=p_christ@hol.gr \
--cc=patrizio.bassi@gmail.com \
--cc=perex@suse.cz \
--cc=sanjoy@mrao.cam.ac.uk \
--cc=tiwai@suse.de \
--cc=torvalds@osdl.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