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 58B012765EB for ; Thu, 28 Aug 2025 18:59:03 +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=1756407543; cv=none; b=g12wDIYCbaYsjWrPSvPKQg318kWraanOAzpGzCiaNvGvw/PpiON94BAS8C6UIdEpTH2H/x+3dJ2MyQ2Xym8m4GtFc/JcQhPxU/5FJH8JvHpAx15zQV4+O5ajX62r/Y3Kj7Ntx38rLGXsmfBz4piVWnf8x0eX5MAxZtRjdBZvEp4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756407543; c=relaxed/simple; bh=Mv8l62t2XOt7GSZpL20Y9pWek5tsA4WaArTWYzhoRAs=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=FHKhi9QMyx8yGU0YVuC8xnFNZ87qbVDoVHz/uOV2SjyH2it8O+ixONifHuAQ1ZE4VullzoF9TTWJ60PFcIp80O45tU+nBHwMqLxD6g0KI3tF+0I+YktsRPFZ7Y/Aw5uEXnD7eR0HJk3irYaYNmk7etfFsCe4dkWxuqP27lhmtV8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Hk2nQRd+; 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="Hk2nQRd+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C5921C4CEED; Thu, 28 Aug 2025 18:59:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1756407542; bh=Mv8l62t2XOt7GSZpL20Y9pWek5tsA4WaArTWYzhoRAs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Hk2nQRd+0oOJR7lrbvBhyXIV9/+WTTWopAkaqUBGst168W1WJn19NifBDzfLVHlEB Z+l/VNGy6clff0zMHU/XLN8KLtsIg3rBmEVAEQNk78Uc4WaT/JO8vGfccXlyFT+71l FKvvTOGpdRuyJhCPl7gqeSIBaCugbmVxdjM31mq3KfOEc/5YZMShHPE2qEOyeW6DuI E+ZyJ/koJ54ffLEH/Z/GbwN+v+xRGQQG07Nc9zHkwHl76bCb1ubpPhhpYISlSP9Ef8 MvVpKSDUwV9U7Xpw+kZiNAJv3ATcv5M24xL4sECKjB0mh4A5A+Vt4dM8lbPKIx2a1Q up6kriuXhWp/Q== Date: Thu, 28 Aug 2025 11:59:01 -0700 From: Luis Chamberlain To: Chuck Lever Cc: "kdevops@lists.linux.dev" Subject: Re: ansible.cfg pathname setting Message-ID: References: <0e9b12aa-64f5-44db-af50-03779b590182@oracle.com> Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0e9b12aa-64f5-44db-af50-03779b590182@oracle.com> On Thu, Aug 28, 2025 at 12:41:08PM -0400, Chuck Lever wrote: > Any opinions about this idea? I can build it if folks agree to it. I tend to just run my own new make defconfig-foo in each directory for each workload, so I have opinion on this, but it sounds like perhaps a kconfig option is desirable, to perhaps opt-in to let it use current working directory for the file? But if it was not generated then via make then what would it use? Ie, if you're shaing a built .config to other directories without making make then it sounds like a requirement is to also share the generated ansible config? Luis