Linux Documentation
 help / color / mirror / Atom feed
From: Karl Mehltretter <kmehltretter@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Thomas Gleixner <tglx@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/7] docs: irq-affinity: Restore grep in example
Date: Sat, 22 Aug 2026 14:16:46 +0200	[thread overview]
Message-ID: <20260822121651.1559-3-kmehltretter@gmail.com> (raw)
In-Reply-To: <20260822121651.1559-1-kmehltretter@gmail.com>

The command is missing grep between the pipe and its pattern.

Fixes: 18404756765c ("genirq: Expose default irq affinity mask (take 3)")
Assisted-by: Codex:gpt-5.6-sol
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
 Documentation/core-api/irq/irq-affinity.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/core-api/irq/irq-affinity.rst b/Documentation/core-api/irq/irq-affinity.rst
index 9cb460cf60b61..671604c7395fe 100644
--- a/Documentation/core-api/irq/irq-affinity.rst
+++ b/Documentation/core-api/irq/irq-affinity.rst
@@ -53,7 +53,7 @@ Now lets restrict that IRQ to CPU(4-7).
 	--- hell ping statistics ---
 	2779 packets transmitted, 2777 packets received, 0% packet loss
 	round-trip min/avg/max = 0.1/0.5/585.4 ms
-	[root@moon 44]# cat /proc/interrupts |  'CPU\|44:'
+	[root@moon 44]# cat /proc/interrupts | grep 'CPU\|44:'
 		CPU0       CPU1       CPU2       CPU3      CPU4       CPU5        CPU6       CPU7
 	44:       1068       1785       1785       1783      1784       1069        1070       1069   IO-APIC-level  eth1
 
-- 
2.53.0


  parent reply	other threads:[~2026-08-22 12:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 12:16 [PATCH 0/7] docs: core-api: Fix stale function names and a broken example Karl Mehltretter
2026-08-22 12:16 ` [PATCH 1/7] docs: cpu_hotplug: Fix multi-instance removal calls Karl Mehltretter
2026-08-22 17:25   ` Randy Dunlap
2026-08-24 16:57   ` Jonathan Corbet
2026-08-24 18:05     ` Karl Mehltretter
2026-08-24 18:28       ` Jonathan Corbet
2026-08-22 12:16 ` Karl Mehltretter [this message]
2026-08-22 17:25   ` [PATCH 2/7] docs: irq-affinity: Restore grep in example Randy Dunlap
2026-08-22 12:16 ` [PATCH 3/7] docs: dma-attributes: Fix dma_alloc_attrs() name Karl Mehltretter
2026-08-22 17:25   ` Randy Dunlap
2026-08-24  9:26   ` Marek Szyprowski
2026-08-22 12:16 ` [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper Karl Mehltretter
2026-08-22 17:26   ` Randy Dunlap
2026-08-22 12:16 ` [PATCH 5/7] docs: this_cpu_ops: Fix SRCU helper names Karl Mehltretter
2026-08-22 16:39   ` Paul E. McKenney
2026-08-22 17:28   ` Randy Dunlap
     [not found] ` <20260822121651.1559-7-kmehltretter@gmail.com>
2026-08-22 12:28   ` [PATCH 6/7] docs: xarray: Fix xas_try_split() name Zi Yan
2026-08-22 17:30   ` Randy Dunlap
     [not found] ` <20260822121651.1559-8-kmehltretter@gmail.com>
2026-08-22 17:32   ` [PATCH 7/7] docs: debugobjects: Fix debug_object_init() name 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=20260822121651.1559-3-kmehltretter@gmail.com \
    --to=kmehltretter@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@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