From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934352AbaFTEp7 (ORCPT ); Fri, 20 Jun 2014 00:45:59 -0400 Received: from mail-ve0-f171.google.com ([209.85.128.171]:44869 "EHLO mail-ve0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932561AbaFTEp6 (ORCPT ); Fri, 20 Jun 2014 00:45:58 -0400 MIME-Version: 1.0 In-Reply-To: <20140619213952.058255809@goodmis.org> References: <20140619213329.478113470@goodmis.org> <20140619213952.058255809@goodmis.org> Date: Thu, 19 Jun 2014 18:45:57 -1000 X-Google-Sender-Auth: 5LCKam_eo2FgEoynRkX1tm4ED84 Message-ID: Subject: Re: [RFC][PATCH 1/3] trace_seq: Move the trace_seq code to lib/ From: Linus Torvalds To: Steven Rostedt Cc: Linux Kernel Mailing List , Ingo Molnar , Andrew Morton , Jiri Kosina , Michal Hocko , Jan Kara , Frederic Weisbecker , Dave Anderson , Petr Mladek Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 19, 2014 at 11:33 AM, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" > > The trace_seq functions are rather useful outside of tracing. They are? Why and where? And why are they still called "trace_xyz()" then? That commit message is useless and contains no actual information. Linus