From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Shankari Anand <shankari.ak0208@gmail.com>
Cc: rust-for-linux@vger.kernel.org, patches@lists.linux.dev,
Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>, Gary Guo <gary@garyguo.net>,
Roy Baron <bjorn3_gh@protonmail.com>,
Benno Lossin <lossin@kernel.org>,
Andreas Hindborg <a.hindborg@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Trevor Gross <tmgross@umich.edu>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v2 1/2] rust: move ARef and AlwaysRefCounted to sync::aref
Date: Wed, 25 Jun 2025 12:57:11 +0200 [thread overview]
Message-ID: <CANiq72=gL_2Q7cbi3+VNLqVPaZzOJ+vCg-b3eDPSPtuwtCzWxA@mail.gmail.com> (raw)
In-Reply-To: <CAPRMd3ncagoKUyy=3aEZndDeVpbnrME9G7dc4jM1Vv+ArQJzXw@mail.gmail.com>
On Wed, Jun 25, 2025 at 12:43 PM Shankari Anand
<shankari.ak0208@gmail.com> wrote:
>
> Adding in the lists.
No, adding them now is not enough -- the patches need to reach the
lists (otherwise I could have done it for you in my previous reply).
In addition, your reply (the one I am replying to) didn't seem to
arrive either, likely because you used HTML.
Also, please include linux-kernel (or did you remove it for some reason?).
> Yes, I rebased the repository to the recent HEAD in the rust-next. There was only one conflict (a commit adding a module to sync.rs) where in I had to accept the combination. Rest seemed to be fine.
Sounds good. For the next time, please mention it in the changelog,
i.e. that part is more important than the `--base` mention, and avoids
people having to do a range diff etc. to notice what changed.
Thanks!
Cheers,
Miguel
next parent reply other threads:[~2025-06-25 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250625101805.645133-1-shankari.ak0208@gmail.com>
[not found] ` <CANiq72nvnqeeteLvhgf-ZfSQN4M_dKKBB41DuOKoboV5an=1Tw@mail.gmail.com>
[not found] ` <CAPRMd3ncagoKUyy=3aEZndDeVpbnrME9G7dc4jM1Vv+ArQJzXw@mail.gmail.com>
2025-06-25 10:57 ` Miguel Ojeda [this message]
2025-06-25 11:11 [PATCH v2 1/2] rust: move ARef and AlwaysRefCounted to sync::aref Shankari Anand
2025-06-25 22:29 ` Benno Lossin
2025-06-26 13:55 ` Shankari Anand
2025-07-02 11:01 ` kernel test robot
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='CANiq72=gL_2Q7cbi3+VNLqVPaZzOJ+vCg-b3eDPSPtuwtCzWxA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--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=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=shankari.ak0208@gmail.com \
--cc=tmgross@umich.edu \
/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).