From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 74446C4708D for ; Wed, 7 Dec 2022 10:57:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229515AbiLGK5H (ORCPT ); Wed, 7 Dec 2022 05:57:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229437AbiLGK5H (ORCPT ); Wed, 7 Dec 2022 05:57:07 -0500 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C14D72F037 for ; Wed, 7 Dec 2022 02:57:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670410626; x=1701946626; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=2rsxH4ACzPvM+rJR86GFeCsgEYXdPBgFuOZ/NAQA0VU=; b=DKtGiK7UnAI6M5Un90CsXb4U8tPK1MBZmokiRsdxDF1/fvvTY+7QdO6H 83GlDXTnOsuDlyWdOoVqJPlA9YjN4aH76zSDP/h/T4awq26NH9yZSrFZ2 xvyQMvi/1T4hEn3gZxz1f/IhleoakGI/O17g5Oyx6LNK+ld7eOBSB2QJr hK3UlE06+GfebIR7Fn3CvmKiEaeyZxJPuDGc3IOafjAQVarAyeYDqSVs0 rE19MjeHQQgr1woO3XCHQBU3r7PsRHfTMre/s90l5w1BBAvszzKIHC1P5 YGA0s4o5YEuUvj4ueGHs71CKXMMxS1+VNNAcsU90SIGiO9Ysk9kLU+0zv Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10553"; a="304493305" X-IronPort-AV: E=Sophos;i="5.96,225,1665471600"; d="scan'208";a="304493305" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Dec 2022 02:57:06 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10553"; a="771062216" X-IronPort-AV: E=Sophos;i="5.96,225,1665471600"; d="scan'208";a="771062216" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga004.jf.intel.com with ESMTP; 07 Dec 2022 02:57:04 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1p2s6o-005jDt-2a; Wed, 07 Dec 2022 12:57:02 +0200 Date: Wed, 7 Dec 2022 12:57:02 +0200 From: Andy Shevchenko To: Bartosz Golaszewski Cc: Kent Gibson , Linus Walleij , Viresh Kumar , linux-gpio@vger.kernel.org, Bartosz Golaszewski Subject: Re: [libgpiod][PATCH 2/2] bindings: python: tests: set the process name Message-ID: References: <20221207091413.61616-1-brgl@bgdev.pl> <20221207091413.61616-2-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221207091413.61616-2-brgl@bgdev.pl> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Wed, Dec 07, 2022 at 10:14:13AM +0100, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > When we run the test suite by calling the __main__ function of the module, > the name of the process as visible in the system becomes "python". Let's > set it to "python-gpiod" before running the tests. This way gpiosim will > name its configfs attributes appropriately. Perhaps you can refer to the [1] to explain why it's needed in Python. Also it can be done via ctype module [2][3] or via module [4], although I haven't checked if most used distros pack it. [1]: https://bugs.python.org/issue5672 [2]: https://stackoverflow.com/a/923034 [3]: https://stackoverflow.com/a/31134436 [4]: https://github.com/dvarrazzo/py-setproctitle -- With Best Regards, Andy Shevchenko