From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, Robert Moore <robert.moore@intel.com>,
Alexey Starikovskiy <alexey.y.starikovskiy@intel.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: udev broken by recent ACPI git commits
Date: Wed, 1 Nov 2006 11:47:41 +0100 [thread overview]
Message-ID: <200611011147.42498.rjw@sisk.pl> (raw)
In-Reply-To: <200611010335.02948.len.brown@intel.com>
On Wednesday, 1 November 2006 09:35, Len Brown wrote:
> > > One of the following commits out of the git-acpi tree breaks udev on my box
> > > (HPC nx6325 w/ 64-bit SUSE 10.1):
>
> I've removed the acpica branch from the acpi test tree for now
> so it doesn't block testing of unrelated patches.
>
> Rafael,
> Please confirm that linus + the new acpi test tree works:
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git test
> here's a plain patch:
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.19/acpi-test-20060707-2.6.19-rc3.diff.gz
Confirmed.
> Please confirm that linus + just the acpica branch fails:
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git acpica
> here's a plain patch:
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.19/acpi-acpica-20061011-2.6.19-rc3.diff.gz
Confirmed too. [Note: It didn't apply cleanly, I had to do one small
adjustment of a printk() in arch/x86_64/pci/mmconfig.c]
> Yes, except for a few small changes, this is the moral equivalent of the bisect that you just did.
No big deal. :-)
> But as Andrew has bounced git-acpi.patch out of -mm, it seems prudent to
> do this check before asking him to pull it in again.
next prev parent reply other threads:[~2006-11-01 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 23:04 udev broken by recent ACPI git commits Rafael J. Wysocki
2006-11-01 5:16 ` Len Brown
2006-11-01 8:35 ` Len Brown
2006-11-01 10:47 ` Rafael J. Wysocki [this message]
2006-11-01 13:03 ` Alexey Starikovskiy
2006-11-01 17:44 ` Rafael J. Wysocki
2006-11-01 19:27 ` Alexey Starikovskiy
2006-11-01 20:00 ` Rafael J. Wysocki
2006-11-02 0:12 ` Henrique de Moraes Holschuh
2006-11-03 5:39 ` Len Brown
2006-11-03 7:58 ` Rafael J. Wysocki
2006-11-03 8:22 ` Rafael J. Wysocki
2006-11-13 11:16 ` Len Brown
2006-11-13 20:56 ` Rafael J. Wysocki
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=200611011147.42498.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=alexey.y.starikovskiy@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.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