From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Keng-Yu Lin <keng-yu.lin@canonical.com>
Cc: len.brown@intel.com, alan-jenkins@tuffmail.co.uk,
superm1@ubuntu.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dell-laptop: Add debugfs support
Date: Mon, 27 Sep 2010 15:00:28 +0100 [thread overview]
Message-ID: <20100927140028.GB856@srcf.ucam.org> (raw)
In-Reply-To: <1285325323-4528-1-git-send-email-keng-yu.lin@canonical.com>
What's the difference between this version and v3?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-09-27 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTime84o+hJWVDegQWHxcvUiftKW-2psW5tv4a-yR@mail.gmail.com>
2010-09-16 3:19 ` [PATCH v2] dell-laptop: Add debugfs support Keng-Yu Lin
2010-09-16 16:46 ` Len Brown
2010-09-17 5:47 ` Keng-Yü Lin
2010-09-17 5:47 ` [PATCH v3] " Keng-Yu Lin
2010-09-24 10:48 ` [PATCH v4] " Keng-Yu Lin
2010-09-27 14:00 ` Matthew Garrett [this message]
2010-09-28 2:43 ` Keng-Yü Lin
2010-09-28 2:52 ` Matthew Garrett
2010-09-28 3:43 ` [PATCH v5] " Keng-Yu Lin
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=20100927140028.GB856@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=keng-yu.lin@canonical.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@ubuntu.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