From: "Danilo Krummrich" <dakr@kernel.org>
To: "Shankari Anand" <shankari.ak0208@gmail.com>
Cc: "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>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn 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>
Subject: Re: [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref
Date: Fri, 01 Aug 2025 10:36:44 +0200 [thread overview]
Message-ID: <DBQYD7G5SOZA.2MSKKQWXTPCBB@kernel.org> (raw)
In-Reply-To: <CAPRMd3nQSyXB+K2Fcs7WJJmtY2F7sm8tFOD1PrkQyHgND=Ju1w@mail.gmail.com>
On Thu Jul 31, 2025 at 7:50 PM CEST, Shankari Anand wrote:
> On Thu Jul 31, 2025 at 14:54 UTC, Danilo Krummrich wrote:
>>
>> Ok, did you send the other ones already? I don't see them anywhere.
>
> The commit 07dad44aa9a9 ("rust: kernel: move ARef and AlwaysRefCounted
> to sync::aref ") refers to the patch where ARef and AlwaysRefCounted
> were moved into a different file. [1]
> To update the call-sites accordingly, I was advised to split the
> changes by subsystem so each patch could be reviewed and acked by the
> respective maintainers. [2]
> These patches are all part of that same effort, although they aren't
> shown as a formal series since the subject lines vary to reflect the
> specific files they touch. [3] [4] [5] [6] [7]
>
>> NIT: Please don't top post. [1]
>
>> [1] https://docs.kernel.org/process/submitting-patches.html#use-trimmed-interleaved-replies-in-email-discussions
>
> Apologies, I’ll make sure to follow the interleaved style.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=07dad44aa9a93b16af19e8609a10b241c352b440
> [2] https://lore.kernel.org/rust-for-linux/CANiq72=NSRMV_6UxXVgkebmWmbgN4i=sfRszr-G+x3W5A4DYOg@mail.gmail.com/T/#u
> [3] https://lore.kernel.org/rust-for-linux/20250716090712.809750-1-shankari.ak0208@gmail.com/
> [4] https://lore.kernel.org/rust-for-linux/20250716091158.812860-1-shankari.ak0208@gmail.com/
> [5] https://lore.kernel.org/rust-for-linux/20250716091827.816971-1-shankari.ak0208@gmail.com/
> [6] https://lore.kernel.org/rust-for-linux/20250717072724.14602-1-shankari.ak0208@gmail.com/
> [7] https://lore.kernel.org/rust-for-linux/20250717073108.14943-1-shankari.ak0208@gmail.com/
Ok, I see what happened. :)
I think you may have misunderstood the suggested of splitting things "by
subsystem". Let's take [7] and [8] for instance.
In [7] you update all the samples, regardless of their subsystem affinity and
[8] updates everything under rust/kernel/.
However, the idea was to send a separate patch per maintainers entry / tree,
such that all patches can be picked in the corresponding tree.
For instance, one patch should be everything that goes through driver-core:
auxiliary, PCI (incl. sample), platform (incl. sample), device, devres.
Then you have another patch for only DMA (incl. sample), etc.
Can you please resend accordingly? Ideally, wait for -rc1 to be out, or base
your changes on -next.
[8] https://lore.kernel.org/lkml/20250717073450.15090-1-shankari.ak0208@gmail.com/
next prev parent reply other threads:[~2025-08-01 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:09 Shankari Anand
2025-07-31 13:37 ` Shankari Anand
2025-07-31 13:52 ` Danilo Krummrich
2025-07-31 13:59 ` Shankari Anand
2025-07-31 14:54 ` Danilo Krummrich
2025-07-31 17:50 ` Shankari Anand
2025-08-01 8:36 ` Danilo Krummrich [this message]
2025-08-13 14:28 ` "Re: [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref" Shankari Anand
2025-08-13 16:31 ` Danilo Krummrich
2025-08-13 16:38 ` [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref Danilo Krummrich
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=DBQYD7G5SOZA.2MSKKQWXTPCBB@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shankari.ak0208@gmail.com \
--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 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®