From: Neil Horman <nhorman@tuxdriver.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: PATCH 0/2 tmon: fix a few minor security issues
Date: Tue, 1 Jul 2014 11:02:59 -0400 [thread overview]
Message-ID: <20140701150259.GI7322@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1404222565.8366.32.camel@rzhang1-toshiba>
On Tue, Jul 01, 2014 at 09:49:25PM +0800, Zhang Rui wrote:
> On Tue, 2014-07-01 at 07:42 -0400, Neil Horman wrote:
> > On Tue, Jun 17, 2014 at 04:05:07PM -0400, Neil Horman wrote:
> > > Just a few little fixups for tmon, to prevent abuse of its logging facility
> > >
> > > Best
> > > Neil
> > >
> > Ping, Zhang, Jacob acked these, but I've not seen them go into your tree yet.
> > Do you have an issue with them?
> >
> Oh, next time when you send thermal related patches, please send them to
> linux-pm@vger.kernel.org mailing list so that I can review the patches
> in https://patchwork.kernel.org/project/linux-pm/list/
>
> Both patches applied. Thanks!
>
Will do, thanks!
Nei
> -rui
> > Neil
> >
> > > --
> > > 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:[~2014-07-01 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 20:05 Neil Horman
2014-06-17 20:05 ` [PATCH 1/2] tmon: Check log file for common secuirty issues Neil Horman
2014-06-17 21:13 ` Jacob Pan
2014-06-17 20:05 ` [PATCH 2/2] tmon: set umask to a reasonable value Neil Horman
2014-06-17 21:14 ` Jacob Pan
2014-06-17 21:15 ` PATCH 0/2 tmon: fix a few minor security issues Jacob Pan
2014-07-01 11:42 ` Neil Horman
2014-07-01 13:49 ` Zhang Rui
2014-07-01 15:02 ` Neil Horman [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=20140701150259.GI7322@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®