From: Thomas Gleixner <tglx@linutronix.de>
To: Takahiro Itazuri <zulinx86@gmail.com>,
linux-doc@vger.kernel.org, corbet@lwn.net
Cc: zulinx86@gmail.com, bp@alien8.de, jani.nikula@linux.intel.com,
jpoimboe@kernel.org, linux-kernel@vger.kernel.org,
pawan.kumar.gupta@linux.intel.com, peterz@infradead.org
Subject: Re: [PATCH v3] Documentation: Unify format for vuln sysfs
Date: Tue, 10 Sep 2024 14:26:51 +0200 [thread overview]
Message-ID: <87wmjjae44.ffs@tglx> (raw)
In-Reply-To: <20240908172341.571476-1-zulinx86@gmail.com>
On Sun, Sep 08 2024 at 17:23, Takahiro Itazuri wrote:
> The format for vuln sysfs files was diverge across pages. Unifies the
> format as follows:
What is a vuln sysfs file?
Can we please avoid random acronyms and abbreviations in change logs?
There is enough space and it's not twatter.
Thanks
tglx
prev parent reply other threads:[~2024-09-10 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 17:23 [PATCH v3] Documentation: Unify format for vuln sysfs Takahiro Itazuri
2024-09-10 1:43 ` Bagas Sanjaya
2024-09-10 12:26 ` Thomas Gleixner [this message]
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=87wmjjae44.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=zulinx86@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.