From: Palmer Dabbelt <palmer@sifive.com>
To: linux-kernel@vger.kernel.org
Cc: corbet@lwn.net, Palmer Dabbelt <palmer@sifive.com>,
aou@eecs.berkeley.edu, ren_guo@c-sky.com,
andrea.parri@amarulasolutions.com, Arnd Bergmann <arnd@arndb.de>,
jhogan@kernel.org, dhowells@redhat.com, jcmvbkbc@gmail.com,
keescook@chromium.org, yamada.masahiro@socionext.com,
mathieu.desnoyers@efficios.com, mingo@kernel.org,
rmk+kernel@armlinux.org.uk, Will Deacon <will.deacon@arm.com>,
jglisse@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
david.abdurachmanov@gmail.com
Subject: Re-run features-refresh.sh
Date: Mon, 12 Nov 2018 18:01:06 -0800 [thread overview]
Message-ID: <20181113020113.29640-1-palmer@sifive.com> (raw)
I didn't even know this existed until David submitted a patch set that
included updates to the documentation as a result of some features he
added to RISC-V. It looks like there may be a handful of other people
who don't know this exists either, so I figured I'd just mail out a
patch set containing all the updates split out as well as I can.
This smells like something that sholud be automatic, so if I'm jumping
the gun here then feel free to drop this. If nobody says anything then
I guess I'll submit this as a separate PR to Linus from my personal
tree, as it's not really a RISC-V thing but it seems like it's worth
having docs that match the code where it's trivial -- I assume that's
what this does, I didn't actually read anything but the diff because I
never trust documentation to be up to date...
I feel compelled to say something like "maybe this should be part of
checkpatch?", but I'm definately not looking to learn perl :)
next reply other threads:[~2018-11-13 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 2:01 Palmer Dabbelt [this message]
2018-11-13 2:01 ` [PATCH 1/7] doc: features-refresh.sh for csky Palmer Dabbelt
2018-11-13 2:01 ` [PATCH 2/7] doc: Indicate that s390 supports KASAN Palmer Dabbelt
2018-11-13 2:01 ` [PATCH 3/7] doc: Indicate that powerpc supports stackprotector Palmer Dabbelt
2018-11-13 2:01 ` [PATCH 4/7] doc: Indicate that xtensa supports sg-chain Palmer Dabbelt
2018-11-13 2:13 ` Max Filippov
2018-11-13 2:01 ` [PATCH 5/7] doc: Indicate that arm64 support queued-spinlocks Palmer Dabbelt
2018-11-13 2:01 ` [PATCH 6/7] doc: Indicate that parisc supports kprobes-events Palmer Dabbelt
2018-11-13 2:01 ` [PATCH 7/7] doc: Indicate that RISC-V support pte_special Palmer Dabbelt
2018-11-13 11:25 ` [PATCH] Documentation/features: Refresh the features list to v4.20-rc2 Ingo Molnar
2018-11-14 17:53 ` Palmer Dabbelt
2018-11-15 9:12 ` Re-run features-refresh.sh Christoph Hellwig
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=20181113020113.29640-1-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=david.abdurachmanov@gmail.com \
--cc=dhowells@redhat.com \
--cc=jcmvbkbc@gmail.com \
--cc=jglisse@redhat.com \
--cc=jhogan@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=ren_guo@c-sky.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).