From: Joe Konno <joe.konno at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH v2 6/8] Stop buffer overflow
Date: Wed, 15 Oct 2014 08:55:00 -0700 [thread overview]
Message-ID: <543E98D4.9050308@linux.intel.com> (raw)
In-Reply-To: 20141015154218.GM1189@swordfish
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
On 10/15/2014 08:42 AM, Sergey Senozhatsky wrote:
> Joe, care to take a second look at those buffer overruns?
All review feedback for this series will be addressed over the next few
days.
This is a "spare time" effort for me, so I can't promise
grease-lightning turn-around.
next reply other threads:[~2014-10-15 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 15:55 Joe Konno [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-15 15:42 [Powertop] [PATCH v2 6/8] Stop buffer overflow Sergey Senozhatsky
2014-10-15 15:24 Arjan van de Ven
2014-10-15 15:19 Sergey Senozhatsky
2014-10-15 15:01 Sergey Senozhatsky
2014-10-15 15:01 Arjan van de Ven
2014-10-15 14:46 Sergey Senozhatsky
2014-10-15 14:34 Arjan van de Ven
2014-10-15 14:21 Sergey Senozhatsky
2014-10-15 14:05 Arjan van de Ven
2014-10-15 14:03 Sergey Senozhatsky
2014-10-15 13:55 Sergey Senozhatsky
2014-10-15 12:54 Sergey Senozhatsky
2014-10-14 18:09 Joe Konno
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=543E98D4.9050308@linux.intel.com \
--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.