From: Len Brown <lenb@kernel.org>
To: "Thomas, Sujith" <sujith.thomas@intel.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH]1/3 intel_menlow:Adding comment for GTHS legal values
Date: Thu, 06 Nov 2008 20:35:41 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811062030280.3106@localhost.localdomain> (raw)
In-Reply-To: <7D0189F5BE1DF549A570B212D1D5612182AF02@bgsmsx412.gar.corp.intel.com>
Hi Sujith,
I applied 1/3 and 2/3.
I had to hand-edit them because they were line wrapped
by your mailer.
This is only a minor waste of my time for a trivial patch,
but for a longer patch, I'm not going to do that for you.
Please read Documentation/SubmittingPatches
note that it is [PATCH 1/3], not [PATCH] 1/3 -- as future
generations don't need the '1/3' in the commit message...
thanks,
-Len
ps. also, don't bother sending a copy of patches to my intel.com
address, that goes to exchange, which destroys patches.
I apply all patches from my kernel.org account, which is
subscribed to the lists.
On Wed, 5 Nov 2008, Thomas, Sujith wrote:
> Documentation of legal values for GTHS
> To be patched over Rui's 09/11 bug fix patch
>
> Signed-off-by: Sujith Thomas <sujith.thomas@intel.com>
> ---
> drivers/misc/intel_menlow.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> Index: linux-2.6.27/drivers/misc/intel_menlow.c
> ===================================================================
> --- linux-2.6.27.orig/drivers/misc/intel_menlow.c
> +++ linux-2.6.27/drivers/misc/intel_menlow.c
> @@ -52,6 +52,11 @@ MODULE_LICENSE("GPL");
> #define MEMORY_ARG_CUR_BANDWIDTH 1
> #define MEMORY_ARG_MAX_BANDWIDTH 0
>
> +/*
> + * GTHS returning 'n' would mean that [0,n-1] states are supported
> + * In that case max_cstate would be n-1
> + * GTHS returning '0' would mean that no bandwidth control states are
> supported
> + */
> static int memory_get_int_max_bandwidth(struct thermal_cooling_device
> *cdev,
> unsigned long *max_state)
> {
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2008-11-07 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 10:45 [PATCH]1/3 intel_menlow:Adding comment for GTHS legal values Thomas, Sujith
2008-11-05 10:45 ` Thomas, Sujith
2008-11-06 23:47 ` Andrew Morton
2008-11-06 23:47 ` Andrew Morton
2008-11-07 1:35 ` Len Brown [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=alpine.LFD.2.00.0811062030280.3106@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sujith.thomas@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 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.