mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Brown, Len" <len.brown@intel.com>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
	acpi-devel@lists.sourceforge.net,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@osdl.org>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	"Yu, Luming" <luming.yu@intel.com>, "Greg KH" <greg@kroah.com>
Subject: Re: Linux v2.6.13-rc3
Date: Thu, 21 Jul 2005 12:09:45 +0200	[thread overview]
Message-ID: <200507211209.46039.rjw@sisk.pl> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B30041AC76D@hdsmsx401.amr.corp.intel.com>

Hi,

On Thursday, 21 of July 2005 07:30, Brown, Len wrote:
> >Len, ACPI people - can we fix this regression, please?
> >
> >Rafael even pinpoints exactly which patches are causing the 
> >problem, so why didn't they get reverted before sending them off to me?
> 
> Linus,
> I'm sorry it was in '-rc3' -- that is as soon as I could
> muster the bk->git transition.  Now that I'm running on git,
> I expect I'll be able to get the development/testing/push
> pipeline moving and back on schedule.
> 
> Yes, we discovered both of these regressions in mm.
> Yes, Rafael has been a sport in filing good bug reports,
> and his Asus L5D has been an interesting case.
> 
> Although we broke this system, I do believe that there is
> significant value in keeping these changes in the mainline,
> as I believe that it is the fastest path to improved support
> for all systems.  Specifically...

In short: If the changes are generally needed, I can live with them
(as long as I know what patches to revert :-)).

Still it would be nice to let people know what to do if they have problems with
these changes.  Many people don't run -rc kernels and even more people
don't run -mm, so they have no idea that there are known regressions  ...

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-07-21 10:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21  5:30 Brown, Len
2005-07-21 10:09 ` Rafael J. Wysocki [this message]
2005-07-21 15:30   ` try acpi -V & acpi -V & acpi -V (was Linux v2.6.13-rc3) Romano Giannetti
2005-07-21 15:41     ` Romano Giannetti
  -- strict thread matches above, loose matches on Subject: below --
2005-07-22  5:28 Linux v2.6.13-rc3 Brown, Len
     [not found] <Pine.LNX.4.58.0507122157070.17536@g5.osdl.org.suse.lists.linux.kernel>
2005-07-13 12:32 ` Andi Kleen
2005-07-13  5:05 Linus Torvalds
2005-07-13  6:21 ` Russell King
2005-07-13 10:59 ` Rafael J. Wysocki
2005-07-13 18:53   ` Linus Torvalds
2005-07-13 19:45     ` Jose Luis Domingo Lopez
2005-07-13 14:27 ` Dmitry Torokhov
2005-07-13 17:31 ` Lee Revell
2005-07-13 17:51   ` Linus Torvalds
2005-07-13 18:05     ` Lee Revell
2005-07-13 22:18 ` Sebastian Kaergel
2005-08-04 21:04   ` Andrew Morton
2005-07-17 11:18 ` Borislav Petkov
2005-07-17 12:40   ` Alexey Dobriyan

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=200507211209.46039.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@intel.com \
    --cc=shaohua.li@intel.com \
    --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

all inboxes | Powered by JetHome®