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 0B6E930F88 for ; Wed, 11 Oct 2023 16:20:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ZtOlTZuS" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 168B9C433C7; Wed, 11 Oct 2023 16:20:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1697041200; bh=pDTAJVGHavfQ67VUhwWXW0cMR4HQ7pEiXLr3viT1UXc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ZtOlTZuSuGbLi1NwDc5StOXMpomx7qnjtGwJR7Fp/v+KE+e5hn3cCIa6Bvm0skU2d 5U+LYPnHRPFY6w4fBwQ+FeZM6lTRaB5F9BADCxuCpXKLOMa/eaFeLcaSLbyD+6pyaH xG9dFCJVH9fgQr4LPjSPpRlmenlS7VGJbGe+x0oTwIadSIVG75XnNJGzC1zNT0wrUt efS9PmG3y+KW6auGfrOw27GS2gQRNjC9/WaDe1GbS6yYZVOuRNQ9sxb+VZb74TFV+e PdtVzFFFHslyWBMgjKalN3OXbeSbD++oX2+xxkyT/KsxmyyR3acSlRT3MfhKpsOL+m 4X8A+bJ9bxZDg== Date: Wed, 11 Oct 2023 09:19:59 -0700 From: Jakub Kicinski To: Johannes Berg Cc: netdev@vger.kernel.org, nicolas.dichtel@6wind.com, fw@strlen.de, pablo@netfilter.org, jiri@resnulli.us, mkubecek@suse.cz, aleksander.lobakin@intel.com, Thomas Haller Subject: Re: [RFC] netlink: add variable-length / auto integers Message-ID: <20231011091959.48010d43@kernel.org> In-Reply-To: <9c70c71cecf19a50c56ed57c0f99660a3176d11d.camel@sipsolutions.net> References: <20231011003313.105315-1-kuba@kernel.org> <20231011090859.3fc30812@kernel.org> <9c70c71cecf19a50c56ed57c0f99660a3176d11d.camel@sipsolutions.net> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 11 Oct 2023 18:16:42 +0200 Johannes Berg wrote: > > I was planning to add the docs to Documentation/userspace-api/netlink/ > > Is that too YNL-specific? > > Oh. I guess I keep expecting that header files at least have some hints, > but whatever ... experience tells me anyway that nobody bothers reading > the comments and people just copy stuff from elsewhere, so we just have > to get this right first in one place ;-) I'll try to add something in the header, in that case. The netlink.h headers are particularly non-conducive to finding stuff since we have 3 of them :(