All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky at gmail.com>
To: powertop@lists.01.org
Subject: [Powertop] introduce powertop2 -next
Date: Tue, 17 Sep 2013 22:30:33 +0300	[thread overview]
Message-ID: <20130917193033.GC2289@swordfish> (raw)

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

Hello everybody,

I've forked a powertop2-next (well, let it be our -next) from the current
code and dig through the list from February 2013 to September 2013 and
picked up all patches that haven't been merged. so we have better chances
not to lose them (we'll merge them with the upstream some day)

URL:  https://github.com/sergey-senozhatsky/powertop2-next

WARNING: the rule remains the same - we use mailing list to publish and discuss
patches, please no github pull requests, etc.



shortlog at the moment is as follows:

Hans-Peter Deifel (2):
      Use symbolic instead of numeric constants for keys
      Document key bindings in man page

Sergey Senozhatsky (5):
      Suppress decimal constant compilation warning (From: Paul Menzel <paulepanter(a)users.sourceforge.net>)
      Seg Fault due to function format_watts in file src/lib.cpp
      Do not leak fd in perf_bundle read_file()
      README: add CONFIG_DEBUG_FS to Kernel Parameters
      Introduce --auto-tune mode

Youquan Song (1):
      Fix running failure when > 69 CPUs for open file limitation




Daniel Kahn Gillmor's 'embed self-contained javascript' patch has some minor
issues at the moment.


NOTE: if you feel that your patch has been lost, please kindly rebase and resend.

Thanks,
        -ss

             reply	other threads:[~2013-09-17 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 19:30 Sergey Senozhatsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-23 19:13 [Powertop] introduce powertop2 -next Kristen Carlson Accardi
2013-09-23 19:27 Sergey Senozhatsky
2013-10-08 21:58 Kristen Carlson Accardi
2013-10-09  9:03 Sergey Senozhatsky
2013-10-09 10:01 Sergey Senozhatsky

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=20130917193033.GC2289@swordfish \
    --to=powertop@lists.01.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 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.