All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"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>,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 1/2] rust: zerocopy: fix link to upstream `README.md`
Date: Wed, 14 Oct 2026 19:41:34 +0000	[thread overview]
Message-ID: <as_a7h-v6eE6P_Yk@google.com> (raw)
In-Reply-To: <20261013184809.35143-1-ojeda@kernel.org>

On Tue, Oct 13, 2026 at 08:48:07PM +0200, Miguel Ojeda wrote:
> Upstream moved the `zerocopy` crate into a `zerocopy/` subdirectory
> of their repository in v0.8.51 [1]. However, in our v0.8.52 update,
> the link was not updated.
> 
> Fix it by adding the subdirectory.
> 
> Fixes: 2808a3963988 ("rust: zerocopy: update to v0.8.52")
> Link: https://github.com/google/zerocopy/pull/3434 [1]
> Assisted-by: LLM
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

For both patches:

Reviewed-by: Alice Ryhl <aliceryhl@google.com>

      parent reply	other threads:[~2026-10-14 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 18:48 [PATCH 1/2] rust: zerocopy: fix link to upstream `README.md` Miguel Ojeda
2026-10-13 18:48 ` [PATCH 2/2] rust: zerocopy: update to v0.8.62 Miguel Ojeda
2026-10-14 19:41 ` Alice Ryhl [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=as_a7h-v6eE6P_Yk@google.com \
    --to=aliceryhl@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --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 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.