From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Durgadoss R <durgadoss.r@intel.com>
Cc: linux-acpi@vger.kernel.org, lenb@kernel.org, rui.zhang@intel.com
Subject: Re: [PATCH 2/2] ACPI-Thermal: Add a 'flag' argument in thermal.c
Date: Thu, 26 Jan 2012 13:42:56 +0000 [thread overview]
Message-ID: <20120126134256.GA11017@srcf.ucam.org> (raw)
In-Reply-To: <1327595749-17673-2-git-send-email-durgadoss.r@intel.com>
On Thu, Jan 26, 2012 at 10:05:49PM +0530, Durgadoss R wrote:
> This patch adds a 'flag' argument to the thermal_zone_device_register
> call in thermal.c.
Functions and callers must be updated in the same patch - if someone
bisects to between these two then their build will be broken.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-01-26 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:35 [PATCH 1/2] ACPI-Thermal: Make Thermal trip points writeable Durgadoss R
2012-01-26 16:35 ` [PATCH 2/2] ACPI-Thermal: Add a 'flag' argument in thermal.c Durgadoss R
2012-01-26 13:42 ` Matthew Garrett [this message]
2012-01-26 16:14 ` R, Durgadoss
2012-01-26 16:23 ` Matthew Garrett
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=20120126134256.GA11017@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=durgadoss.r@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@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).