From: John Hubbard <jhubbard@nvidia.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Greg KH" <greg@kroah.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
linux-kbuild@vger.kernel.org, rust-for-linux@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"John Hubbard" <jhubbard@nvidia.com>
Subject: [PATCH v2 0/2] Makefile: rust-analyzer better error handling, documentation
Date: Thu, 20 Jun 2024 13:54:51 -0700 [thread overview]
Message-ID: <20240620205453.81799-1-jhubbard@nvidia.com> (raw)
Changes since v1:
1) Thanks to Alice Ryhl for testing and reviewing v1. I had to drop both
of those tags for this v2, because even though it is small, it's
different enough to invalidate both, unfortunately.
2) Adopted Miguel Ojeda's suggestion of letting rust_is_available.sh
report its results directly, thus improving the output, while also
simplifying the patch.
3) As requested by Miguel, split out some new comment documentation
for the rust-analyzer target into its own patch.
John Hubbard (2):
Makefile: rust-analyzer target: better error handling
Makefile: improve comment documentation for the rust-analyzer target
Makefile | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
base-commit: e5b3efbe1ab1793bb49ae07d56d0973267e65112
--
2.45.2
next reply other threads:[~2024-06-20 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 20:54 John Hubbard [this message]
2024-06-20 20:54 ` [PATCH v2 1/2] Makefile: rust-analyzer target: better error handling John Hubbard
2024-06-25 18:59 ` Finn Behrens
2024-06-26 8:00 ` Alice Ryhl
2024-06-20 20:54 ` [PATCH v2 2/2] Makefile: improve comment documentation for the rust-analyzer target John Hubbard
2024-06-25 19:00 ` Finn Behrens
2024-06-26 8:08 ` Alice Ryhl
2024-06-26 8:42 ` Miguel Ojeda
2024-06-27 1:46 ` John Hubbard
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=20240620205453.81799-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=greg@kroah.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@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 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).