mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	oss-drivers@netronome.com, Divya Indi <divya.indi@oracle.com>
Subject: Re: [PATCH 0/3] tracing: fix minor build warnings
Date: Fri, 30 Aug 2019 18:01:50 -0400	[thread overview]
Message-ID: <20190830180150.687f3ec8@gandalf.local.home> (raw)
In-Reply-To: <20190828052549.2472-1-jakub.kicinski@netronome.com>

On Tue, 27 Aug 2019 22:25:46 -0700
Jakub Kicinski <jakub.kicinski@netronome.com> wrote:

> Hi!
> 
> trace.o gets rebuild on every make run when tracing is enabled,
> which makes all warnings particularly noisy. This patchset fixes
> some low-hanging fruit on W=1 C=1 builds.
> 
> Jakub Kicinski (3):
>   tracing: correct kdoc formats

I took the first one, but the two below, I wont take. Those changes
were added in preparation of the kernel access to tracing code.

See:

  http://lkml.kernel.org/r/1565805327-579-1-git-send-email-divya.indi@oracle.com

-- Steve


>   tracing: remove exported but unused trace_array_destroy()
>   tracing: make trace_array_create() static
> 
>  kernel/trace/trace.c | 47 ++++++++++++++------------------------------
>  1 file changed, 15 insertions(+), 32 deletions(-)
> 


  parent reply	other threads:[~2019-08-30 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  5:25 Jakub Kicinski
2019-08-28  5:25 ` [PATCH 1/3] tracing: correct kdoc formats Jakub Kicinski
2019-08-28  5:25 ` [PATCH 2/3] tracing: remove exported but unused trace_array_destroy() Jakub Kicinski
2019-08-28  5:25 ` [PATCH 3/3] tracing: make trace_array_create() static Jakub Kicinski
2019-08-30 22:01 ` Steven Rostedt [this message]
2019-08-30 22:38   ` [PATCH 0/3] tracing: fix minor build warnings Jakub Kicinski

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=20190830180150.687f3ec8@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=divya.indi@oracle.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oss-drivers@netronome.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®