All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Huang Hake-B20222 <B20222@freescale.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>, cpufreq@vger.kernel.org
Subject: Re: FW: [PATCH 1/4] pass the cross to bench folder
Date: Fri, 27 May 2011 11:53:46 +0200	[thread overview]
Message-ID: <201105271153.46959.trenn@suse.de> (raw)
In-Reply-To: <A809BCB44791BE4D97606D7DA1807F411127EF@039-SN1MPN1-002.039d.mgd.msft.net>

Hi Huang,

On Wednesday, May 25, 2011 09:01:19 AM Huang Hake-B20222 wrote:
> Hi,
> 
> I see your cpupower project and want to port it to ARM, can I send patch
> to you, see below mail
Great.
Did you google my (private) email address?

Dominik has set up a git repo which is already synced against
linux-next and the stuff will (hopefully) show up in the mainline
kernel soon.
Best is you base patches against this kernel repo:
http://git.kernel.org/?p=linux/kernel/git/brodo/cpupowerutils.git;a=summary
The code is located in tools/power/cpupower
and send it to the cpufreq@vger.kernel.org list with Dominik in CC.

For architecture (ARM/ACPI/...) specific problems you may also
want add other Linux kernel lists
(http://vger.kernel.org/vger-lists.html) for broader review.
Should not be needed for these, just for info.

Please also add:
cpupower:
(upper case?) as prefix to the subject on cpupower related patches.

If you add me to CC (I won't be able to comment/review on these patches, 
though), please use trenn@suse.de.

Thanks,

    Thomas


       reply	other threads:[~2011-05-27  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A809BCB44791BE4D97606D7DA1807F411127EF@039-SN1MPN1-002.039d.mgd.msft.net>
2011-05-27  9:53 ` Thomas Renninger [this message]
2011-05-27 10:01   ` FW: [PATCH 1/4] pass the cross to bench folder Huang Hake-B20222

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=201105271153.46959.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=B20222@freescale.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /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.