From: Jiri Slaby <jirislaby@gmail.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: please git pull ACPI for 2.6.17
Date: Sun, 14 May 2006 20:00:31 +0159 [thread overview]
Message-ID: <44677056.1080004@gmail.com> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB670F3C4@hdsmsx411.amr.corp.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brown, Len napsal(a):
>> is it possible to do so now, still before .17 release?
>
> I think that on April 3rd this was appropriate.
> But now 6 weeks later in the release cycle I don't think it is
> appropriate to do such a large pull.
It seemed obvious, I just tried it, because there was a complain on bugzilla.
>
> I'm assuming this tree will not be pulled until the start of .18.
Never mind.
>
> Jiri,
> Is there a specific individual patch that you are wanting to have in
> .17?
I wanted to have ecdt-uid-hack there, because asus laptops' acpi is defunct, but
as I said, it doesn't matter, 2.6.18-rc1 is not so far.
thanks,
- --
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEZ3BWMsxVwznUen4RAsk4AKDEhjpLcItL1v1MXe7ZShvTLUmONACgqpG9
uQPOD1X8gS9SX0C2avn8Hj8=
=l1s/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-14 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 17:08 please git pull ACPI for 2.6.17 Brown, Len
2006-05-14 17:08 ` Brown, Len
2006-05-14 18:01 ` Jiri Slaby [this message]
2006-06-17 21:18 ` Resume on Apple Mac Mini Linus Torvalds
2006-06-18 0:35 ` Linus Torvalds
2006-06-18 13:25 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 22:06 please git pull ACPI for 2.6.17 Len Brown
2006-05-14 14:13 ` Jiri Slaby
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=44677056.1080004@gmail.com \
--to=jirislaby@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.