From: Charalampos Mitrodimas <charmitro@posteo.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Onur Özkan" <work@onurozkan.dev>,
rust-for-linux@vger.kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, yutaro.ono.418@gmail.com,
borys.tyran@protonmail.com, daniel@sedlak.dev, tamird@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] rbtree: reduce unsafe blocks on pointer derefs
Date: Mon, 19 Jan 2026 08:36:52 +0000 [thread overview]
Message-ID: <87a4yac82m.fsf@posteo.net> (raw)
In-Reply-To: <CANiq72mrJ8yF-LVuXbsz3z_Sf3d3AXk2J_NbGNeu9Nsfgg8Zbw@mail.gmail.com>
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:
> On Mon, Nov 17, 2025 at 1:13 PM Charalampos Mitrodimas
> <charmitro@posteo.net> wrote:
>>
>> This is a nice change to have if it reaches the general consensus.
>>
>> Acked-By: Charalampos Mitrodimas <charmitro@posteo.net>
>
> So, typically, Acked-by tags are given by maintainers of the code.
> Sometimes, other stakeholders give it too:
>
> https://docs.kernel.org/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
>
> I will keep the tag, but if this was meant to be a Reviewed-by or
> similar instead, please let me know.
Hi Miguel,
I was not aware, thanks for the heads up! Assume it is a Reviewed-by or
just discard since it's invalid.
>
> (Nit: it is usually -by, not -By).
Ah yes, need to update my email client snippet configuration.
C. Mitrodimas
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2026-01-19 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 14:45 [PATCH v1] rbtree: reduce unsafe blocks on pointer derefs Onur Özkan
2025-11-17 12:13 ` Charalampos Mitrodimas
2026-01-18 21:03 ` Miguel Ojeda
2026-01-19 8:36 ` Charalampos Mitrodimas [this message]
2026-01-19 8:39 ` Miguel Ojeda
2026-01-14 8:42 ` Alice Ryhl
2026-01-18 21:02 ` Miguel Ojeda
2026-01-18 21:27 ` Alice Ryhl
2026-01-19 8:21 ` Miguel Ojeda
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=87a4yac82m.fsf@posteo.net \
--to=charmitro@posteo.net \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=borys.tyran@protonmail.com \
--cc=dakr@kernel.org \
--cc=daniel@sedlak.dev \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=yutaro.ono.418@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 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.