From: "Björn Töpel" <bjorn@kernel.org>
To: Celeste Liu <uwu@coelacanthus.name>,
Oleg Nesterov <oleg@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
"Dmitry V. Levin" <ldv@strace.io>,
Andrea Bolognani <abologna@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, Ron Economos <re@w6rz.net>,
Felix Yan <felixonmars@archlinux.org>,
Ruizhe Pan <c141028@gmail.com>,
Shiqi Zhang <shiqi@isrc.iscas.ac.cn>, Guo Ren <guoren@kernel.org>,
Yao Zi <ziyao@disroot.org>, Han Gao <gaohan@iscas.ac.cn>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH] riscv/ptrace: add new regset to get original a0 register
Date: Tue, 03 Dec 2024 12:23:01 +0100 [thread overview]
Message-ID: <87jzchdn8q.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <31d48f53-eaf0-445e-b9e3-7c56070ff6ad@coelacanthus.name>
Celeste Liu <uwu@coelacanthus.name> writes:
>>> +static int riscv_orig_a0_get(struct task_struct *target,
>>> + const struct user_regset *regset,
>>> + struct membuf to)
>>
>> Use full 100 chars!
>
> Linux code style prefer 80 limit.
No, it has been increased to 100, since many years [1].
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/scripts/checkpatch.pl#n60
next prev parent reply other threads:[~2024-12-03 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 21:47 Celeste Liu
2024-12-02 15:44 ` Björn Töpel
2024-12-03 9:33 ` Celeste Liu
2024-12-03 11:23 ` Björn Töpel [this message]
2024-12-03 5:37 ` Charlie Jenkins
2024-12-03 9:41 ` Celeste Liu
2024-12-03 12:19 ` Dmitry V. Levin
2024-12-03 18:45 ` Charlie Jenkins
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=87jzchdn8q.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=abologna@redhat.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=c141028@gmail.com \
--cc=ebiederm@xmission.com \
--cc=felixonmars@archlinux.org \
--cc=gaohan@iscas.ac.cn \
--cc=guoren@kernel.org \
--cc=kees@kernel.org \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=re@w6rz.net \
--cc=shiqi@isrc.iscas.ac.cn \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=uwu@coelacanthus.name \
--cc=ziyao@disroot.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