From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Petr Mladek" <pmladek@suse.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"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@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/4] Check Rust signatures at compile time
Date: Fri, 28 Feb 2025 14:26:49 +0200 [thread overview]
Message-ID: <Z8GriWN4C-e3583T@smile.fi.intel.com> (raw)
In-Reply-To: <20250227-export-macro-v1-0-948775fc37aa@google.com>
On Thu, Feb 27, 2025 at 05:01:58PM +0000, Alice Ryhl wrote:
This is unfortunate. What does this mean?
Can you, please, provide a meaningful cover letter?
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-02-28 12:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <UXTosjUFv_CKOV-K4oqNGBhMEv64tds9NgXWhHEYdCHuKM2qSPFrpBnTqhFGkcbv5_KXYERykIXhn-sYnEeuUg==@protonmail.internalid>
2025-02-27 17:01 ` [PATCH 0/4] Check Rust signatures at compile time Alice Ryhl
2025-02-27 17:01 ` [PATCH 1/4] rust: fix signature of rust_fmt_argument Alice Ryhl
2025-02-28 8:13 ` Andreas Hindborg
2025-02-28 8:44 ` Alice Ryhl
2025-02-28 9:17 ` Andreas Hindborg
2025-02-27 17:02 ` [PATCH 2/4] rust: add #[export] macro Alice Ryhl
2025-02-28 8:12 ` Andreas Hindborg
2025-02-28 9:04 ` Alice Ryhl
2025-02-28 9:24 ` Andreas Hindborg
2025-02-27 17:02 ` [PATCH 3/4] print: use new #[export] macro for rust_fmt_argument Alice Ryhl
2025-02-28 8:15 ` Andreas Hindborg
2025-02-27 17:02 ` [PATCH 4/4] panic_qr: use new #[export] macro Alice Ryhl
2025-02-27 21:28 ` Boqun Feng
2025-02-27 23:01 ` Alice Ryhl
2025-02-28 8:19 ` Andreas Hindborg
2025-02-27 19:30 ` [PATCH 0/4] Check Rust signatures at compile time Greg Kroah-Hartman
2025-02-27 23:03 ` Alice Ryhl
2025-02-28 8:47 ` Alice Ryhl
2025-02-28 7:19 ` Andreas Hindborg
2025-02-28 8:46 ` Alice Ryhl
2025-02-28 9:18 ` Andreas Hindborg
2025-02-28 12:27 ` Andy Shevchenko
2025-02-28 12:26 ` Andy Shevchenko [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=Z8GriWN4C-e3583T@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ojeda@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
/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.