All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/4] tracing: More updates for 5.13
Date: Sat, 03 Apr 2021 10:33:47 -0400	[thread overview]
Message-ID: <20210403143347.409590683@goodmis.org> (raw)

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: ceaaa12904df07d07ea8975abbf04c4d60e46956


Linus Torvalds (1):
      ftrace: Store the order of pages allocated in ftrace_page

Steven Rostedt (VMware) (1):
      ftrace: Simplify the calculation of page number for ftrace_page->records some more

Wan Jiabing (1):
      tracing: Remove duplicate struct declaration in trace_events.h

Yordan Karadzhov (VMware) (1):
      tracing: Remove unused argument from "ring_buffer_time_stamp()

----
 include/linux/ring_buffer.h  |  2 +-
 include/linux/trace_events.h |  1 -
 kernel/trace/ftrace.c        | 45 +++++++++++++++++++-------------------------
 kernel/trace/ring_buffer.c   |  2 +-
 kernel/trace/trace.c         |  8 ++++----
 5 files changed, 25 insertions(+), 33 deletions(-)

             reply	other threads:[~2021-04-03 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 14:33 Steven Rostedt [this message]
2021-04-03 14:33 ` [for-next][PATCH 1/4] tracing: Remove duplicate struct declaration in trace_events.h Steven Rostedt
2021-04-03 14:33 ` [for-next][PATCH 2/4] tracing: Remove unused argument from "ring_buffer_time_stamp() Steven Rostedt
2021-04-03 14:33 ` [for-next][PATCH 3/4] ftrace: Store the order of pages allocated in ftrace_page Steven Rostedt
2021-04-03 14:33 ` [for-next][PATCH 4/4] ftrace: Simplify the calculation of page number for ftrace_page->records some more Steven Rostedt

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=20210403143347.409590683@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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.