From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] i7z: new package
Date: Wed, 27 Apr 2016 22:14:51 +0200 [thread overview]
Message-ID: <20160427221451.0d2fa3ed@free-electrons.com> (raw)
In-Reply-To: <1461762764-8559-1-git-send-email-vincent.stehle@intel.com>
Hello,
On Wed, 27 Apr 2016 15:12:44 +0200, Vincent Stehl? wrote:
> "A better i7 (and now i3, i5) reporting tool for Linux."
>
> i7z can print out the C-states and temperature for i3, i5 and i7 based Core
> processors from Intel (including Nehalems, Sandy Bridge and Ivy Bridge).
>
> https://github.com/ajaiantilal/i7z
>
> Signed-off-by: Vincent Stehl? <vincent.stehle@intel.com>
> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
Applied to master, thanks.
However, I don't know if you had a look at the source code itself. But
it is really truly horrible. I think I had never seen a function taking
34 arguments, so much code WRITTEN ALMOST ENTIRELY IN CAPS and
generally such an atrocity. And I'm used to looking at vendor code in
Linux BSPs, so I'm somewhat used to all sort of atrocities.
https://github.com/ajaiantilal/i7z/blob/master/i7z_Dual_Socket.c
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-27 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:21 [Buildroot] [PATCH] i7z: new package Vincent Stehlé
2016-04-26 14:55 ` Bernd Kuhls
2016-04-27 7:39 ` Vincent Stehlé
2016-04-27 8:05 ` Thomas Petazzoni
2016-04-26 15:17 ` Bernd Kuhls
2016-04-27 8:13 ` Vincent Stehlé
2016-04-27 9:25 ` [Buildroot] [PATCH v2] " Vincent Stehlé
2016-04-27 9:36 ` Bernd Kuhls
2016-04-27 13:12 ` [Buildroot] [PATCH v3] " Vincent Stehlé
2016-04-27 20:14 ` Thomas Petazzoni [this message]
2016-04-27 20:56 ` Peter Korsgaard
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=20160427221451.0d2fa3ed@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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.