From: Andrew Morton <akpm@osdl.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Greg KH <greg@kroah.com>, Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.19-rc3-mm1 - udev doesn't work (was: ATI SATA controller not detected)
Date: Mon, 30 Oct 2006 23:58:50 -0800 [thread overview]
Message-ID: <20061030235850.cb3a40ed.akpm@osdl.org> (raw)
In-Reply-To: <200610310848.02739.rjw@sisk.pl>
On Tue, 31 Oct 2006 08:48:01 +0100
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > > It's one of these:
> > >
> > > git-acpi.patch
> > > git-acpi-fixup.patch
> > > git-acpi-more-build-fixes.patch
> > >
> >
> > You might need to resend the original report so the acpi guys can see it.
>
> Okay, I will.
Thanks.
> > Meanwhile, I'll have to drop the acpi tree.
>
> Well, I'd prefer to find the offending commit within the tree, as the majority
> of changes look pretty innocent. Are the commits available somewhere as
> individual patches?
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git#test
I've not had much success persuading git to emit a series of applyable
patches.
next prev parent reply other threads:[~2006-10-31 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061029160002.29bb2ea1.akpm@osdl.org>
[not found] ` <200610302148.34218.rjw@sisk.pl>
[not found] ` <20061030205742.GA4084@kroah.com>
2006-10-31 0:19 ` 2.6.19-rc3-mm1 - udev doesn't work (was: ATI SATA controller not detected) Rafael J. Wysocki
2006-10-31 7:29 ` Rafael J. Wysocki
2006-10-31 7:40 ` Andrew Morton
2006-10-31 7:48 ` Rafael J. Wysocki
2006-10-31 7:58 ` Andrew Morton [this message]
2006-11-02 2:29 ` 2.6.19-rc3-mm1 - udev doesn't work Andy Whitcroft
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=20061030235850.cb3a40ed.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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