From: Matthew Garrett <matthew.garrett@nebula.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Harald Welte <laforge@gnumonks.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH 1/3] platform/x86: panasonic-laptop: reuse module_acpi_driver
Date: Tue, 3 Sep 2013 12:07:05 +0000 [thread overview]
Message-ID: <1378210024.11730.5.camel@x230> (raw)
In-Reply-To: <1377690523-3511-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Wed, 2013-08-28 at 14:48 +0300, Andy Shevchenko wrote:
> +module_acpi_driver(&acpi_pcc_driver);
module_acpi_driver(acpi_pcc_driver), right? I've fixed that and applied.
--
Matthew Garrett <matthew.garrett@nebula.com>
next prev parent reply other threads:[~2013-09-03 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 11:48 [PATCH 1/3] platform/x86: panasonic-laptop: reuse module_acpi_driver Andy Shevchenko
2013-08-28 11:48 ` [PATCH 2/3] platform/x86: intel-smartconnect: " Andy Shevchenko
2013-08-28 11:48 ` [PATCH 3/3] platform/x86: intel-rst: " Andy Shevchenko
2013-09-03 12:07 ` Matthew Garrett [this message]
2013-09-03 12:27 ` [PATCH 1/3] platform/x86: panasonic-laptop: " Andy Shevchenko
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=1378210024.11730.5.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=laforge@gnumonks.org \
--cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox