linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Bristot de Oliveira <bristot@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org
Subject: [PATCH 0/4] trace: osnoise tracer fixes
Date: Mon, 28 Jun 2021 11:45:46 +0200	[thread overview]
Message-ID: <cover.1624872608.git.bristot@redhat.com> (raw)

Fixes problems reported by kernel test robot <lkp@intel.com>, and
a typo in the documentation.

No functional change.

Daniel Bristot de Oliveira (4):
  trace/osnoise: Fix 'no previous prototype' warnings
  trace/osnoise: Make interval u64 on osnoise_main
  trace/osnoise: Fix return value on osnoise_init_hotplug_support
  Documentation: Fix a typo on trace/osnoise-tracer

 Documentation/trace/osnoise-tracer.rst |  2 +-
 arch/x86/kernel/trace.c                |  3 ---
 include/linux/trace.h                  |  2 ++
 kernel/trace/trace_osnoise.c           | 24 +++++++++++++-----------
 4 files changed, 16 insertions(+), 15 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-06-28  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28  9:45 Daniel Bristot de Oliveira [this message]
2021-06-28  9:45 ` [PATCH 1/4] trace/osnoise: Fix 'no previous prototype' warnings Daniel Bristot de Oliveira
2021-06-28  9:45 ` [PATCH 2/4] trace/osnoise: Make interval u64 on osnoise_main Daniel Bristot de Oliveira
2021-06-28  9:45 ` [PATCH 3/4] trace/osnoise: Fix return value on osnoise_init_hotplug_support Daniel Bristot de Oliveira
2021-06-28  9:45 ` [PATCH 4/4] Documentation: Fix a typo on trace/osnoise-tracer Daniel Bristot de Oliveira

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=cover.1624872608.git.bristot@redhat.com \
    --to=bristot@redhat.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).