From: Corentin Chary <corentin.chary@gmail.com>
To: Yong Wang <yong.y.wang@linux.intel.com>
Cc: cascardo@holoscopio.com, Matthew Garrett <mjg59@srcf.ucam.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] eeepc-wmi: new driver for WMI based hotkeys on Eee PC laptops
Date: Sun, 21 Mar 2010 14:55:01 +0100 [thread overview]
Message-ID: <71cd59b01003210655l785dba6fh527b1f90e0b670c5@mail.gmail.com> (raw)
In-Reply-To: <20100321133524.GA17060@ywang-moblin2.bj.intel.com>
On Sun, Mar 21, 2010 at 2:35 PM, Yong Wang <yong.y.wang@linux.intel.com> wrote:
> On Sun, Mar 21, 2010 at 02:14:18PM +0100, Corentin Chary wrote:
>>
>> Yep Matthew will merge my tree. Platform x86 subsystem is young, so it
>> only happened once, but I think
>> he will continue to do so. Do you want a write access to acpi4asus
>> tree, or do you want me to merge your tree ?
>>
>
> I don't have a public tree and I don't think I need write access to your
> tree. I will continue to send out patches when I have time to work on
> it. You can pick them up into your tree if you think they look ok to
> you. Is that OK?
>
> Thanks
> -Yong
>
Yep,
--
Corentin Chary
http://xf.iksaif.net
prev parent reply other threads:[~2010-03-21 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100319133924.GA30427@ywang-moblin2.bj.intel.com>
2010-03-19 13:59 ` [PATCH] eeepc-wmi: new driver for WMI based hotkeys on Eee PC laptops Matthew Garrett
2010-03-19 15:10 ` Yong Wang
2010-03-19 15:23 ` Matthew Garrett
2010-03-19 15:21 ` Yong Wang
2010-03-20 0:55 ` Yong Wang
2010-03-20 12:20 ` cascardo
2010-03-20 12:24 ` Yong Wang
2010-03-20 17:21 ` Corentin Chary
2010-03-21 0:59 ` Yong Wang
2010-03-21 13:14 ` Corentin Chary
2010-03-21 13:35 ` Yong Wang
2010-03-21 13:55 ` Corentin Chary [this message]
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=71cd59b01003210655l785dba6fh527b1f90e0b670c5@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=cascardo@holoscopio.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=yong.y.wang@linux.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;
as well as URLs for NNTP newsgroup(s).