From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 766542EAB72; Thu, 28 May 2026 02:21:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779934893; cv=none; b=mO7HzdDlHIfUQfWhAPvCHtOZSHnoFX7U4bcP/RU06SkCf/F3KQOsL+JRXnHXVkpyHvDHrHJL9vuMQczR5Gk73FSsoJmb/Kdt8/6J9dU+w4L9Lqf0LKUsZGyDcMuYJ/OWbxEz71mlXiYvLGCSPTUiqaMKjzXzUqW6DEcHlsxfR+A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779934893; c=relaxed/simple; bh=dK60yFVR86W5hGG5jfY+yRcEE9ybI5Mf8ONVQV+ZVso=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=asfDIAC3o46CLaY+yedCCtjhmGqO6fnY6GmW8B8+3G1+Tdt97CqQ6rYZyI3qy1c0ZTAU9XG3TyM+S6/WbT2FUCVlg9kTvpit1JFT9Ti7QLR797muDxjtv06X+o/UpT8pZ+oA0VED691vyA9KpzGBLispyaSKOvqfJUkS77/Wh3U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=TyaTWit+; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="TyaTWit+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 676FD1F00A3A; Thu, 28 May 2026 02:21:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779934892; bh=LB5jSSEDEd8ttTdSWGELR3Mewo9+R6WZhATO6rBa85Q=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=TyaTWit+Hs/r7i1hVdfKAJe2iNe+7xGBiqePpqOAvCCa1yRtThRF4re7fPvzpCpvE 4rrgJ5aesn7igwrHHtzvi+HgyC5qDQxIlRIkFeFZHBQXM1VJpy2DNvuSps9a/bR84b 3GtFY39k7vU/WFdrJ/p8MDGg1afQIjliXm6fWPO8Xd64obG93Di/vg7iorqK61iMje cBnnAIkKile9YEg6OaZJ90teQSCR+SDbIxp5JS5WRvKu7pPofKXAIOVYYSJhnnOH7E pckPrT9YeHit/wm3kQTkZlr6DhkcWXwJO8EzyEJq3vkmJUMAHKYZB5lcWJlOsZkwB1 op0P84Jhg+CAg== Date: Wed, 27 May 2026 19:21:30 -0700 From: Jakub Kicinski To: Alice Ryhl Cc: Donald Hunter , Greg Kroah-Hartman , Andrew Lunn , "David S. Miller" , Carlos Llamas , Eric Dumazet , Paolo Abeni , Simon Horman , Matthew Maurer , Miguel Ojeda , Boqun Feng , Gary Guo , "=?UTF-8?B?QmrDtnJu?= Roy Baron" , Benno Lossin , Andreas Hindborg , Trevor Gross , Danilo Krummrich , Christian Brauner , linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH v5 1/2] rust: netlink: add raw netlink abstraction Message-ID: <20260527192130.21dabf08@kernel.org> In-Reply-To: References: <20260525-binder-netlink-v5-0-a90e2923ebeb@google.com> <20260525-binder-netlink-v5-1-a90e2923ebeb@google.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 27 May 2026 10:00:40 +0000 Alice Ryhl wrote: > On Tue, May 26, 2026 at 04:29:26PM +0200, Miguel Ojeda wrote: > > On Mon, May 25, 2026 at 3:17=E2=80=AFPM Alice Ryhl wrote: =20 > > > > > > This implements a safe and relatively simple API over the netlink API, > > > that allows you to add different attributes to a netlink message and > > > broadcast it. As the first user of this API only makes use of broadca= st, > > > only broadcast messages are supported here. =20 > > =20 > > > rust/kernel/netlink.rs | 336 ++++++++++++++++++++++++++++++= ++++++++++ =20 > >=20 > > This should be added to an existing or new `MAINTAINERS` entry, i.e. > > as usual, either inheriting it if the maintainers want, or delegating > > it to a sub- or co-maintainer, etc. depending on what people want. =20 Good call, missed this isn't under rust/kernel/net > Netdev maintainers, what do you prefer that I put for these files? I'm > of course happy to be on the hook for this code. Can we put it under rust/kernel/net and rust/helpers/net ? And then add those directories to networking ? Just so that we don't have to keep wondering with every little piece=20 of code. > We can either add it under an existing entry, or we could add a new one > along these lines: >=20 > NETWORKING [RUST] > M: Alice Ryhl > L: netdev@vger.kernel.org > L: rust-for-linux@vger.kernel.org > S: Supported > F: rust/helpers/genetlink.c > F: rust/kernel/netlink.rs Probably not at this time. > Of course, it would be useful to have others listed here, as I'm sure I > will have questions about how networking works if there are patches in > this area. Or perhaps the netdev@ list itself is enough for that to > reach the right people? >=20 > With regards to actually merging code in this area, then I think for > this particular series it is simpler to let Greg take it through > char-misc with all the other Binder changes. But for any future changes > to netlink.rs, I think it makes sense for them to land through the > netdev tree. SG, once acked it can go via any tree. Greg's tree make sense.