From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22]) (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 E618024C69D for ; Wed, 5 Mar 2025 14:34:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.70.43.22 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741185284; cv=none; b=IczdlLyBEonsozZAVJqNj8e+qXabaF4DDKkwArmV5uyIHvttjjw1L77FKJGBO7QTTJNJPNEOa14p2Knej+4HE113oGMiEmkf/H4GKV3kFHTuDNHMxOXScfeet7hli/53Q44JpKGvYyb8L2I0Whpk0n720Hvai9h02HOi3J0GDeU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741185284; c=relaxed/simple; bh=+3KZycyRQWg6AONdj6MUvhWQ0yttj5flpyUcA4hxWz8=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=dme+TpIWB3Vzx6n9Z+2DVuoqG74oQOoaVV1VS2wc3CwPhrU7tW//Z7RhnunWJWhEBkuWQ75sHBhpD5WLilobeBJ4nbCHO8ZWQne/nvVfK4Z2467jvWUv2NCWUPOnHv2voHP+JEJeQ9jMjR+32HgHTqCp8yTxyUtHXJbCmq8keGE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=proton.me; spf=pass smtp.mailfrom=proton.me; dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me header.b=X+nq+VyV; arc=none smtp.client-ip=185.70.43.22 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=proton.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=proton.me Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me header.b="X+nq+VyV" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=cogdqg55erhcjfmdfg247whv2y.protonmail; t=1741185280; x=1741444480; bh=+3KZycyRQWg6AONdj6MUvhWQ0yttj5flpyUcA4hxWz8=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=X+nq+VyVUTJl6QdqXVEonz5IDPa9VbvjAvmcPlCsjHps5CeP/6HaxVKnCJ7Y4SC9M zLC/D5VHdBgK1qo/Ne32jj7FjEkYxYJ3cfxWfU3Jz7HwXPzBTG5oOP0x4TtSe4sFA2 vrwSUItLtT0Pxp6RSWiBB1hA8O8cwAYx/+jMVduu8Mv2T09ooDQm7Km3c4lGM5zhSb Kai3cw9sdqjjbQcEbEL2sQPjCgd3GiT+k5+pRNL+fauHYqiDjuCeoIhOeIoiVFrxZj /iMYgsKhbmY5ex+74sl2YhcrROOs60341LtJHZ2yLO9/UUV+8IkYhtpe5iZ01TXZ6J AhusOW/Rp4qFw== Date: Wed, 05 Mar 2025 14:34:35 +0000 To: Andreas Hindborg , Miguel Ojeda From: Benno Lossin Cc: Miguel Ojeda , Alex Gaynor , Boqun Feng , Gary Guo , =?utf-8?Q?Bj=C3=B6rn_Roy_Baron?= , Alice Ryhl , Trevor Gross , Danilo Krummrich , Masahiro Yamada , Nathan Chancellor , Nicolas Schier , linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, linux-kbuild@vger.kernel.org Subject: Re: [PATCH 14/22] rust: add pin-init crate build infrastructure Message-ID: In-Reply-To: <878qpja7b5.fsf@kernel.org> References: <20250304225245.2033120-1-benno.lossin@proton.me> <20250304225245.2033120-15-benno.lossin@proton.me> <87h647d6xg.fsf@kernel.org> <87ldtjbqw2.fsf@kernel.org> <878qpja7b5.fsf@kernel.org> Feedback-ID: 71780778:user:proton X-Pm-Message-ID: eb7d669969bb2d542e365fcae0c70997690124b9 Precedence: bulk X-Mailing-List: linux-kernel@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 Mar 5, 2025 at 3:19 PM CET, Andreas Hindborg wrote: > "Miguel Ojeda" writes: > >> On Wed, Mar 5, 2025 at 1:34=E2=80=AFPM Andreas Hindborg wrote: >>> >>> I _really_ think that the ability to run the tests should be present in >>> the kernel repository. But I also do not want to block this series on i= t, >>> if it is something that will be easier to achieve with the build system >>> overhaul that is in the pipeline. >> >> No, that is not the plan. Even with the new build system, this is >> supposed to be developed upstream as far as I understand, so you will >> need to run them there anyway. >> >> Unless there is a reason we could catch more bugs here, that is. > > I guess it would be no different than `syn`. But I think it is a shame > that we move something that people could contribute to via the kernel > development flow - out of the kernel development flow. You *can* send patches via the list, I will pick them up and run them through the GitHub CI. Patches that arrive via GitHub will also go through the list and people can add their tags there. Also I don't think that pin-init will receive a lot of contributions in the first place. I do have a lot of changes planned for when we get `syn`, but other than that, I don't think it will change a lot in the future. --- Cheers, Benno