From: Dave Jones <davej@redhat.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: latest ACPI patch vs 2.6.17-rc4
Date: Fri, 12 May 2006 13:51:47 -0400 [thread overview]
Message-ID: <20060512175147.GA20123@redhat.com> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB66D5B3C@hdsmsx411.amr.corp.intel.com>
On Fri, May 12, 2006 at 01:49:14PM -0400, Brown, Len wrote:
>
> > > Note that I removed the acpi_in_resume workaround, so
> > > you'll get some oops'
> > > during resume, until we replace it with something else.
> >
> >Which you intend to do before .17 final I assume?
> >Seems funny to be ripping something out without a replacement fix.
>
> Hi Dave,
> the acpi patch flow is that the acpi git tree gets pulled into -mm.
>
> patches that survive -mm get cherry picked and sent to linus
> within the 1st two weeks of his release cycle.
>
> (exceptions for critical bug fixes, of course)
>
> So removal of acpi_in_resume is in -mm, but is not in linus,
> and it will not be pushed to linus until this issue is addressed.
> I expect this to take place at the start of .18.
> I don't have any plans to push any significant patches (certainly
> no clean-up patches) to .17.
Ok, I was just having a panic attack fearing the worst when I pushed
out a .17 update for Fedora users :-)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-12 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 17:49 latest ACPI patch vs 2.6.17-rc4 Brown, Len
2006-05-12 17:51 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-14 4:24 Brown, Len
2006-05-12 9:18 Len Brown
2006-05-12 11:37 ` Sergio Monteiro Basto
2006-05-12 13:54 ` Dave Jones
2006-05-14 4:48 ` Len Brown
2006-05-15 8:07 ` Len Brown
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=20060512175147.GA20123@redhat.com \
--to=davej@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.