From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Kris Van Hees" <kris.van.hees@oracle.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Li Zhijian" <lizhijian@fujitsu.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Alcock" <nick.alcock@oracle.com>,
"Tamir Duberstein" <tamird@gmail.com>,
"Vegard Nossum" <vegard.nossum@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] .gitignore: ignore Python compiled bytecode
Date: Wed, 16 Apr 2025 10:16:08 +0300 [thread overview]
Message-ID: <Z_9ZOInQVgx5wtbG@smile.fi.intel.com> (raw)
In-Reply-To: <eb7c854d1bddab19ec1105b928463bb1845d4d50.1744786420.git.mchehab+huawei@kernel.org>
On Wed, Apr 16, 2025 at 02:57:39PM +0800, Mauro Carvalho Chehab wrote:
> While the building system doesn't create any Python JIT bytecode,
> if one manually runs kernel-doc.py or get_abi.py, Python will,
> by default, create a bytecode and store it under scripts/lib/*.
>
> This is normal, and not controlled by the Kernel itself. So,
> add *.pyc as an extension to be ignored.
...
> *.mod.c
> *.o
> *.o.*
> +*.pyc
Shouldn't we prevent the order? (This should go after the "patch")
> *.patch
> *.rmeta
> *.rpm
...
P.S. I'm going to test the first patch (at least) soon.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-04-16 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 6:57 [PATCH v2 0/2] Don't create Python bytecode when building the kernel Mauro Carvalho Chehab
2025-04-16 6:57 ` [PATCH v2 1/2] scripts/kernel-doc.py: don't create *.pyc files Mauro Carvalho Chehab
2025-04-16 7:22 ` Andy Shevchenko
2025-04-16 7:51 ` Mauro Carvalho Chehab
2025-04-16 7:33 ` Jani Nikula
2025-04-16 7:36 ` Jani Nikula
2025-04-16 6:57 ` [PATCH v2 2/2] .gitignore: ignore Python compiled bytecode Mauro Carvalho Chehab
2025-04-16 7:16 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z_9ZOInQVgx5wtbG@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kris.van.hees@oracle.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lizhijian@fujitsu.com \
--cc=masahiroy@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nathan@kernel.org \
--cc=nick.alcock@oracle.com \
--cc=ojeda@kernel.org \
--cc=tamird@gmail.com \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).