From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753859AbcBEP5O (ORCPT ); Fri, 5 Feb 2016 10:57:14 -0500 Received: from mail-wm0-f51.google.com ([74.125.82.51]:37900 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752768AbcBEP5N (ORCPT ); Fri, 5 Feb 2016 10:57:13 -0500 MIME-Version: 1.0 In-Reply-To: <20160205100426.72fa51b2@gandalf.local.home> References: <1445278226-16187-1-git-send-email-0x7f454c46@gmail.com> <20160204214045.1d6c2893@grimm.local.home> <20160205100426.72fa51b2@gandalf.local.home> From: Dmitry Safonov <0x7f454c46@gmail.com> Date: Fri, 5 Feb 2016 18:56:52 +0300 Message-ID: Subject: Re: [RFC] trace_irqsoff: remove redundant reset per-CPU buff To: Steven Rostedt Cc: mingo@redhat.com, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2016-02-05 18:04 GMT+03:00 Steven Rostedt : > Also, FYI, even if you do an RFC, include "PATCH" in the brackets as > well. I usually have "[RFC][PATCH]". Because when I'm looking for > patches in my inbox, I will filter for PATCH. If a patch is out there > without that in the subject, it is much more likely to be missed (and > most likely will). Will do. And I added RFC mostly because, I didn't see the reason for reseting second time, but if it has been (I wasn't sure), I wanted to add a comment, why. -- Regards, Safonov Dmitry.