From: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Jiri Kosina <trivial@kernel.org>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Hauke Mehrtens <hauke@hauke-m.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
Subject: [PATCH v3 0/3] MIPS: kernel: proc: fix style and add CPU option reporting
Date: Wed, 13 Oct 2021 22:40:15 -0700 [thread overview]
Message-ID: <20211014054018.6179-1-ilya.lipnitskiy@gmail.com> (raw)
Fix checkpatch errors and use seq_puts instead of seq_printf where
possible.
Re-send an old patch that adds CPU option reporting.
Tested against MT7621 on OpenWrt running v5.10 kernel.
MT7621 output:
Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc
pindexed_dcache userlocal vint perf_cntr_intr_bit cdmm perf
---
v2: Add missing options that were added since the original patch
v3: Resend after 6 months and add Hauke's Acked-by
Hauke Mehrtens (1):
MIPS: kernel: proc: add CPU option reporting
Ilya Lipnitskiy (2):
MIPS: kernel: proc: fix trivial style errors
MIPS: kernel: proc: use seq_puts instead of seq_printf
arch/mips/kernel/proc.c | 227 ++++++++++++++++++++++++++++++++--------
1 file changed, 184 insertions(+), 43 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-14 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 5:40 Ilya Lipnitskiy [this message]
2021-10-14 5:40 ` [PATCH v3 1/3] MIPS: kernel: proc: fix trivial style errors Ilya Lipnitskiy
2021-10-14 5:40 ` [PATCH v3 2/3] MIPS: kernel: proc: use seq_puts instead of seq_printf Ilya Lipnitskiy
2021-10-14 5:40 ` [PATCH v3 3/3] MIPS: kernel: proc: add CPU option reporting Ilya Lipnitskiy
2021-10-14 6:09 ` [PATCH v3 0/3] MIPS: kernel: proc: fix style and " Sergio Paracuellos
2021-10-14 8:09 ` Serge Semin
2021-10-24 15:33 ` Thomas Bogendoerfer
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=20211014054018.6179-1-ilya.lipnitskiy@gmail.com \
--to=ilya.lipnitskiy@gmail.com \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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®