From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 30B97360; Fri, 1 Aug 2025 08:36:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754037410; cv=none; b=hoeqy5R207dAvyoGIn8lHqGoQQEjpkuGm4QHKO2uhWsryfPXtX+LIvazWs0oB4TKrx1FuVbM3L9F/HMLWBeh90hdyg010Ll7055z1hMHQV9EBabDsd1z9n1LVijtBmRCJu4YJcQm5wjD00anpnvT0BmldsFc8a/+b8H4IW7AruI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754037410; c=relaxed/simple; bh=zTczmumPB6Km92g9PvLzCLzv5zMr/38WTwK+e/y3Q+Q=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=Z1Ot+dEIj8KSgJ2h0oo0s0sWUOeCyvEuDxgnRZVfi3NWzcYcA2oBKRxAX0Z8rx3PH6Nh66Uv8vD/xykYyj2BUIZk0+zl+2FBG18nTKz2uvnNrNbs0IEdXKmT2PjDpGx0Zv0JGSbYxfgMr9MBj74dJXcDm7wysyEu6mUxqKkkrPk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=m4Sdodfg; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="m4Sdodfg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 61A42C4CEE7; Fri, 1 Aug 2025 08:36:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1754037409; bh=zTczmumPB6Km92g9PvLzCLzv5zMr/38WTwK+e/y3Q+Q=; h=Date:Subject:Cc:To:From:References:In-Reply-To:From; b=m4SdodfgihiXdK7otoTKUM7W16maOmMO+sfkzm/gWiAV4cQ/7CiFqpa3jIxVvtYXo kbutMWUmSE0L01asjB4RwvdKCCv02NzBoRzuVitwpa3SXH0ypsLzvcXQ/getrcS+uv TedwXzQMY0Bo3LlTR3VXkXTL490Frxz0j2hxsZO+HM0WQn+nt1pLOvOu9XwpDJ1MEa VSpful51sPOBsVGgLf2QJTTrhbr2nu46co5IyrjpcIoIX4ccR40gbUE414XAxd+gI3 op/ShN/b8DmlHawEB/qu4TiMPeXmholQP0QEShQj8xXb2LXgnMRFJan+YXbVaqq5tv fy81T+atoFr0Q== Precedence: bulk X-Mailing-List: rust-for-linux@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 01 Aug 2025 10:36:44 +0200 Message-Id: Subject: Re: [PATCH 2/7] rust: gpu: update ARef and AlwaysRefCounted imports from sync::aref Cc: "Maarten Lankhorst" , "Maxime Ripard" , "Thomas Zimmermann" , "David Airlie" , "Simona Vetter" , "Miguel Ojeda" , "Alex Gaynor" , , , "Boqun Feng" , "Gary Guo" , =?utf-8?q?Bj=C3=B6rn_Roy_Baron?= , "Benno Lossin" , "Andreas Hindborg" , "Alice Ryhl" , "Trevor Gross" To: "Shankari Anand" From: "Danilo Krummrich" References: <20250716090941.811418-1-shankari.ak0208@gmail.com> In-Reply-To: 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=E2=80=99ll make sure to follow the interleaved style. > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/c= ommit/?id=3D07dad44aa9a93b16af19e8609a10b241c352b440 > [2] https://lore.kernel.org/rust-for-linux/CANiq72=3DNSRMV_6UxXVgkebmWmbg= N4i=3DsfRszr-G+x3W5A4DYOg@mail.gmail.com/T/#u > [3] https://lore.kernel.org/rust-for-linux/20250716090712.809750-1-shanka= ri.ak0208@gmail.com/ > [4] https://lore.kernel.org/rust-for-linux/20250716091158.812860-1-shanka= ri.ak0208@gmail.com/ > [5] https://lore.kernel.org/rust-for-linux/20250716091827.816971-1-shanka= ri.ak0208@gmail.com/ > [6] https://lore.kernel.org/rust-for-linux/20250717072724.14602-1-shankar= i.ak0208@gmail.com/ > [7] https://lore.kernel.org/rust-for-linux/20250717073108.14943-1-shankar= i.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 a= nd [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 bas= e your changes on -next. [8] https://lore.kernel.org/lkml/20250717073450.15090-1-shankari.ak0208@gma= il.com/