Linux Perf Users
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Thomas Gleixner <tglx@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	x86@kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH 1/5] perf/x86/intel/pt: drop kernel-doc for deleted struct members
Date: Thu, 30 Jul 2026 16:34:25 -0700	[thread overview]
Message-ID: <20260730233429.285788-2-rdunlap@infradead.org> (raw)
In-Reply-To: <20260730233429.285788-1-rdunlap@infradead.org>

@lost and @topa_index are no longer part of struct pt_buffer so
delete their comment lines.

Warning: ../arch/x86/events/intel/pt.h:86 Excess struct member 'lost'
 description in 'pt_buffer'
Warning: ../arch/x86/events/intel/pt.h:86 Excess struct member
 'topa_index' description in 'pt_buffer'

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
New patch.

Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Thomas Gleixner <tglx@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Cc: linux-perf-users@vger.kernel.org


 arch/x86/events/intel/pt.h |    2 --
 1 file changed, 2 deletions(-)

--- linux-next-20260722.orig/arch/x86/events/intel/pt.h
+++ linux-next-20260722/arch/x86/events/intel/pt.h
@@ -58,7 +58,6 @@ struct pt_pmu {
  * @cur_idx:	current output region's index within @cur table
  * @output_off:	offset within the current output region
  * @data_size:	running total of the amount of data in this buffer
- * @lost:	if data was lost/truncated
  * @head:	logical write offset inside the buffer
  * @snapshot:	if this is for a snapshot/overwrite counter
  * @single:	use Single Range Output instead of ToPA
@@ -68,7 +67,6 @@ struct pt_pmu {
  * @stop_te:	STOP topa entry pointer
  * @intr_te:	INT topa entry pointer
  * @data_pages:	array of pages from perf
- * @topa_index:	table of topa entries indexed by page offset
  */
 struct pt_buffer {
 	struct list_head	tables;

  reply	other threads:[~2026-07-30 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 23:34 [PATCH 0/5] x86: clean up some kernel-doc comments Randy Dunlap
2026-07-30 23:34 ` Randy Dunlap [this message]
2026-07-30 23:34 ` [PATCH 2/5 RESEND] x86/barrier: use correct parameter names in kernel-doc Randy Dunlap
2026-07-30 23:34 ` [PATCH 3/5 RESEND] x86/lib: checksum_64.h: eliminate all kernel-doc warnings Randy Dunlap
2026-07-30 23:34 ` [PATCH 4/5] x86/speculation: drop Excess function parameter descriptions Randy Dunlap
2026-07-30 23:34 ` [PATCH 5/5] x86/intel/quark: clean up function kernel-doc Randy Dunlap

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=20260730233429.285788-2-rdunlap@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=acme@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --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