From: "Gary Guo" <gary@garyguo.net>
To: "Gary Guo" <gary@garyguo.net>, "Benno Lossin" <lossin@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] rust: pin-init: internal: handle item and expr diagnostics differently
Date: Mon, 28 Sep 2026 12:51:36 +0100 [thread overview]
Message-ID: <DLQXEUPBK9YP.32KOE82CSMXLJ@garyguo.net> (raw)
In-Reply-To: <20260923140618.1978181-1-gary@kernel.org>
Applied to pin-init-next, with R-b tag provided by Benno in person.
95593ed36161 rust: pin-init: internal: improve diagnostics robustness against panicking
rust/pin-init/internal/src/diagnostics.rs | 24 ++++++++++++++++++++++--
1 file changed, 22 insertions(+), 2 deletions(-)
73c1f157907c rust: pin-init: internal: make `DiagCtxt` available inside parser
rust/pin-init/internal/src/diagnostics.rs | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------
rust/pin-init/internal/src/init.rs | 41 ++++++++++++++---------------------------
rust/pin-init/internal/src/lib.rs | 32 +++++++++++++++++---------------
3 files changed, 96 insertions(+), 61 deletions(-)
[ Reflow the long diagnostics message that exceeds 100 columns. ]
01c3d218e8fa rust: pin-init: internal: handle item and expr diagnostics differently
rust/pin-init/internal/src/diagnostics.rs | 55 +++++++++++++++++++++++++++++++++++++++++++++++--------
rust/pin-init/internal/src/lib.rs | 12 ++++++------
2 files changed, 53 insertions(+), 14 deletions(-)
Best,
Gary
prev parent reply other threads:[~2026-09-28 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 14:06 Gary Guo
2026-09-23 14:06 ` [PATCH 2/3] rust: pin-init: internal: make `DiagCtxt` available inside parser Gary Guo
2026-09-23 14:06 ` [PATCH 3/3] rust: pin-init: internal: improve diagnostics robustness against panicking Gary Guo
2026-09-28 11:51 ` Gary Guo [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=DLQXEUPBK9YP.32KOE82CSMXLJ@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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®